sporq/kmk_firmware
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

call out make fix-isort etc before code commit

Browse Source
This commit is contained in:
Hilary B. Brenum 2022-03-15 17:44:05 -07:00 committed by Kyle Brown
parent b2c7da2058
commit 275e61832f
1 changed files with 8 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/contributing.md
View File

@ -14,11 +14,14 @@ This channel is bridged to Discord [here](https://discord.gg/QBHUUpeGUd) for con
KMK uses [Black](https://github.com/psf/black) with a Python 3.6 target and, KMK uses [Black](https://github.com/psf/black) with a Python 3.6 target and,
[(controversially?)](https://github.com/psf/black/issues/594) single quotes. [(controversially?)](https://github.com/psf/black/issues/594) single quotes.
Further code styling is enforced with isort and flake8 with several plugins. Further code styling is enforced with isort and flake8 with several plugins.
`make fix-isort fix-formatting` before a commit is a good idea, and CI will fail
if inbound code does not adhere to these formatting rules. Some exceptions are **NOTE:** before committing code, run `make fix-istort fix-formatting test` to
found in `setup.cfg` loosening the rules in isolated cases, notably reduce workload for the project's maintainers and prevent the CI pipeline from
`user_keymaps` (which is *also* not subject to Black formatting for reasons failing.
documented in `pyproject.toml`).
There are some limited exceptions to the code formatting rules, which can be
found in `setup.cfg`, notably around `user_keymaps` (which are also not subject
to Black formatting as documented in `pyproject.toml`)
### Tests ### Tests