A GitHub :octocat: app to automatically review Python code style over Pull Requests
A GitHub :octocat: app to automatically review Python code style over Pull Requests
pycodestyle
or flake8
as your linter. The bot can read configurations for both.setup.cfg
for [flake8]
and [pycodestyle]
sections. Check out the Configuration
section below.A config file is not required for the integration to work. However it can be configured additionally by adding a .pep8speaks.yml
file in the root of the project. Here is an example :
# File : .pep8speaks.yml
scanner:
diff_only: True # If False, the entire file touched by the Pull Request is scanned for errors. If True, only the diff is scanned.
linter: pycodestyle # Other option is flake8
pycodestyle: # Same as scanner.linter value. Other option is flake8
max-line-length: 100 # Default is 79 in PEP 8
ignore: # Errors and warnings to ignore
- W504 # line break after binary operator
- E402 # module level import not at top of file
- E731 # do not assign a lambda expression, use a def
- C406 # Unnecessary list literal - rewrite as a dict literal.
- E741 # ambiguous variable name
no_blank_comment: True # If True, no comment is made on PR without any errors.
descending_issues_order: False # If True, PEP 8 issues in message will be displayed in descending order of line numbers in the file
message: # Customize the comment made by the bot
opened: # Messages when a new PR is submitted
header:
"Hello @{name}! Thanks for opening this PR. "
# The keyword {name} is converted into the author's username
footer:
"Do see the [Hitchhiker's guide to code style](https://goo.gl/hqbW4r)"
# The messages can be written as they would over GitHub
updated: # Messages when new commits are added to the PR
header: "Hello @{name}! Thanks for updating this PR. "
footer: "" # Why to comment the link to the style guide everytime? :)
no_errors: "There are currently no PEP 8 issues detected in this Pull Request. Cheers! :beers: "
Notes:
.pep8speaks.yml
will override these values..pep8speaks.yml
in the base
branch (the existing one). If the file is not found, it then searches the head
branch (the incoming changes).scanner.linter
to either pycodestyle
or flake8
ignore
or max-line-length
), PEP8Speaks will look and prioritize configurations in the following order :
pycodestyle:
or flake8:
section of .pep8speaks.yml
.
scanner.linter
value.[pycodestyle]
or [flake8]
section of setup.cfg
file in the root of the project.
scanner.linter
. So, [flake8]
section of setup.cfg
will also work for pycodestyle.Organization | Description | |
---|---|---|
Pandas | Powerful data manipulation tools for Python | |
Adobe | Open source from Adobe | |
openSUSE | Linux distribution | |
PyTorch Lightning | The lightweight PyTorch wrapper for ML researchers. | |
NetworkX | Python library for graph theory and complex networks | |
Statsmodels | Statistical modeling and econometrics in Python | |
xarray (PyData) | N-D labeled arrays and datasets in Python (Python for Data) | |
SunPy | Python for Solar Physics | |
Astropy | Astronomy in Python | |
Scikit Learn Contrib | scikit-learn compatible projects | |
Scikit Image | Image processing in Python | |
Spyder IDE | The Scientific Python Development Environment | |
Catalyst | PyTorch framework for Deep Learning research and development |
See the complete list of organizations and users.
@pep8speaks suggest diff
in a comment of the PR, and it will comment a gist of diff suggesting fixes for the PR. Example
@pep8speaks pep8ify
on the PR and it will create a Pull Request with changes suggested by autopep8
against the branch of the author of the PR. autopep8
fixes most of the errors reported by pycodestyle
.[skip pep8]
anywhere in the commit message, PR title or PR description to prohibit pep8speaks from commenting on the Pull Request.This app will only work for publicly hosted repositories. So if you are looking to deploy a fork or use the app for private repositories, here are the instructions.
pep8
).Updates to the app are announced using the GitHub Release feature over here. A lot of major changes are made as the community grows bigger. Click on Watch
-> Releases only
on top of the page, to get notified about new configurations or feature updates.
Usually, the master branch is deployed as soon as Pull Requests are merged in the repository. However, on every Friday, I make a release and make sure the latest code is deployed. You do not need to do anything to use the latest version. If you use a fork of PEP 8 Speaks, check out the Release space.
Become a Gold Sponsor and get your logo and name with a link to your site on our README and our website.
Samagra Governance |
SamagraX |
Become a Gold Sponsor and get your logo and name with a link to your site on our README and our website.
Python Software Foundation |
Weblate |
Become a Silver Sponsor and get your logo and name with a link to your site on our README and our website.
CCExtractor |
Sudhanshu Mishra |
You can support the project by contributing to its development. If you have any suggestions for new features or improvements, please create an issue. Pull Requests are most welcome ! Read CONTRIBUTING doc to understand how the project works and how you can make changes.
The project requires to be hosted on a server and due to which, it needs financial support as well.
Please read the case for funding PEP 8 Speaks.
If you use this project and you like it, please let me know. Thanks!
:heart:
This project does not endorse all of the rules of the original PEP 8 and thus believes in customizing pycodestyle.