pep8speaks is back again!

pep8speaks is up again, install it now! ✨

Our new sponsors Samagra Governance and SamagraX are taking care of the deployment costs for pep8speaks and we have new maintainers @tushar5526 @Mr-Sunglasses. Thanks to @OrkoHunter for making this possible 🚀

Checkout what the bot is up to here 🤖

What's Changed

• Avoid confusing line break in "PEP 8 issues" by @MikhailRyazanov in #177
• Update runtime.txt by @mees in #185
• Dockerize pep8speaks and use gunicorn to deploy by @tushar5526 in #193
• Project is maintained again so removed unmaintaind status from the re… by @Mr-Sunglasses in #198
• Recent activity by @tushar5526 in #204
• Revert "Recent activity" by @tushar5526 in #205
• Recent activity by @tushar5526 in #206
• Revert "Recent activity" by @tushar5526 in #207
• Create DEPLOYMENT-GUIDE.md by @tushar5526 in #202
• Add recent activity in README by @tushar5526 in #208
• feat: Add GHA to build docker images and push to GH packages by @tushar5526 in #209
• [fix]: fixed images in README.md by @Mr-Sunglasses in #210
• Update README.md by @tushar5526 in #212

New Contributors

• @MikhailRyazanov made their first contribution in #177
• @mees made their first contribution in #185
• @tushar5526 made their first contribution in #193
• @Mr-Sunglasses made their first contribution in #198

Full Changelog: v1.8...v1.9

PEP 8 Speaks v1.8

Upgrade pycodestyle and flake8 linter versions to support newer features

PEP 8 Speaks v1.7

• The master branch could not be deployed. Deprecate Flask-Session dependency causing the issue. #167
• Upgrade pytest and pytest-flask version to fix tests.
• Fix bot behavior to make a single comment per PR on non-official deployments
  f91fa62
• Fix errors for PRs with empty description #145

PEP 8 Speaks v1.6

• Allow users to choose their linter. As of now, pycodestyle and flake8 are supported. PR #115
• Pull Requests can now be tested on Travis with confidence. #100
• Added more logging to easily debug.
• Separate local tests from Travis tests
• Built a case for funding.
• Do not use any database to store the installations. But instead, star the project from the bot account.
• Changed default config file of the project from json to yaml
• Installed the auto-comment bot on each PR.
• Installed the weekly digest bot
• Bug fixes.

Pull Requests: #100 #112 #115 #117 #118 #119 #120 #122

PEP8Speaks v1.5

• Users can now use [flake8] or [pycodestyle] section inside their setup.cfg file to configure PEP 8. #95 #106 Read more in the Configuration section in the README
• PEP8Speaks will now look at the head branch of the Pull Request as a fallback if no config is found in the base branch. #55
• By default, only the diff in the PR will be scanned now. The earlier behaviour used to confuse new contributors. 1822b5d
• Minor bug fixes

PEP8Speaks v1.4

• Personal access token of the bot is used now instead of password. PEP8Speaks will now work for bots with 2fa enabled. #78 #79
• Changed license from AGPL to MIT (more permissive)
• Code refactor
• Refactor language used by the bot #92

Thank you @duffn @CAM-Gerlach @mikekutzma @BoboTiG @kohr-h and others for your contributions!

Upgrade Heroku stack

v1.3.2

Upgrade version of PyYAML

Bug fixes

• Fix a major bug in create_gist function #102 #103

A new release

This release changes the design of the integration's action. Checkout this gif to see the new model.

New Features

• All set for Private repositories
• One comment per PR

A new release

New Features

• Use no_blank_comment: True in the config file to stop bot from commenting if no pep8 errors are found

Bug fixes

• Closed #12

Improvements :

• Use the .pep8speaks.yml file from the PR.