All patches and comments are welcome. Please squash your changes to logical
commits before using git-format-patch and git-send-email to
patches@git.madduck.net.
If you'd read over the Git project's submission guidelines and adhered to them,
I'd be especially grateful.
* Update CONTRIBUTION with pre-commit + black-primer instructions
- Inform people how to run primer and alter it's config
- Link to main documentation
* Apply suggestions from code review
Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
Install all development dependencies using:
Install all development dependencies using:
$ pipenv install --dev
$ pipenv shell
$ pre-commit install
$ pipenv install --dev
$ pipenv shell
$ pre-commit install
`pip install pipenv` in the virtualenv you're already using and invoke the command above
from the cloned _Black_ repo. It will do the correct thing.
`pip install pipenv` in the virtualenv you're already using and invoke the command above
from the cloned _Black_ repo. It will do the correct thing.
-Before submitting pull requests, run tests with:
+Before submitting pull requests, run lints and tests with:
+```console
+$ pre-commit run -a
+$ black-primer [-k -w /tmp/black_test_repos]
+## black-primer
+
+`black-primer` is used by CI to pull down well-known _Black_ formatted projects and see
+if we get soure code changes. It will error on formatting changes or errors. Please run
+before pushing your PR to see if you get the actions you would expect from _Black_ with
+your PR. You may need to change
+[primer.json](https://github.com/psf/black/blob/master/src/black_primer/primer.json)
+configuration for it to pass.
+
+For more `black-primer` information visit the
+[documentation](https://github.com/psf/black/blob/master/docs/black_primer.md).
+
## Hygiene
If you're fixing a bug, add a test. Run it first to confirm it fails, then fix the bug,
## Hygiene
If you're fixing a bug, add a test. Run it first to confirm it fails, then fix the bug,