Lines Matching +full:auto +full:- +full:request +full:- +full:review

12 … a bug in pyfakefs, you can [create an issue](https://help.github.com/articles/creating-an-issue/).
13 …bug, please check, if it still exists in the [main branch](https://github.com/pytest-dev/pyfakefs).
20 …rkdown code formatting](https://help.github.com/articles/creating-and-highlighting-code-blocks/) f…
26 Of course - implementing it yourself is the best chance to get it done!
32 [fork](https://help.github.com/articles/fork-a-repo/) the [repository](https://github.com/pytest-de…
33 …on a feature branch, and [create a pull request](https://help.github.com/articles/creating-a-pull-…
35   * We ensure the [PEP-8 coding style](https://www.python.org/dev/peps/pep-0008/)
36     by using [black](https://pypi.org/project/black/) auto-format in a
37     pre-commit hook; you can locally install
38     [pre-commit](https://pypi.org/project/pre-commit/) to run the linter
39     tests on check-in or on demand (`pre-commit run --all-files`)
41   * Provide unit tests for bug fixes or new functionality - check the existing tests for examples
42   * Provide meaningful commit messages - it is ok to amend the commits to improve the comments
43   * Check that the automatic GitHub Action CI tests all pass for your pull request
44   * Be ready to adapt your changes after a code review
48 If you want to improve the existing documentation, you can do this also using a pull request.
51 …ithub.com/pytest-dev/pyfakefs/blob/main/README.md) using [markdown syntax](https://help.github.com…
52 …* the documentation published on [Read the Docs](https://pytest-pyfakefs.readthedocs.io/en/latest/…
55   * [this file](https://github.com/pytest-dev/pyfakefs/blob/main/CONTRIBUTING.md)