mirror of
https://github.com/kovidgoyal/kitty.git
synced 2024-09-11 14:45:31 +03:00
31 lines
1.3 KiB
Markdown
31 lines
1.3 KiB
Markdown
### Reporting bugs
|
|
|
|
Please first search existing bug reports (especially closed ones) for a report
|
|
that matches your issue.
|
|
|
|
When reporting a bug, provide full details of your environment, that means, at
|
|
a minimum, kitty version, OS and OS version, kitty config (ideally a minimal
|
|
config to reproduce the issue with).
|
|
|
|
Note that bugs and feature requests are often closed quickly as they are either
|
|
fixed or deemed wontfix/invalid. In my experience, this is the only scalable way to
|
|
manage a bug tracker. Feel free to continue to post to a closed bug report
|
|
if you would like to discuss the issue further. Being closed does not mean you
|
|
will not get any more responses.
|
|
|
|
### Contributing code
|
|
|
|
Install [the dependencies](https://sw.kovidgoyal.net/kitty/build/#dependencies)
|
|
using your favorite package manager. Build and run kitty [from
|
|
source](https://sw.kovidgoyal.net/kitty/build/#install-and-run-from-source).
|
|
|
|
Make a fork, submit your Pull Request. If it's a large/controversial change, open an issue
|
|
beforehand to discuss it, so that you don't waste your time making a pull
|
|
request that gets rejected.
|
|
|
|
If the code you are submitting is reasonably easily testable, please contribute
|
|
tests as well (see the `kitty_tests/` sub-directory for existing tests, which
|
|
can be run with `./test.py`).
|
|
|
|
That's it.
|