All Versions
10
Latest Version
1.8
Avg Release Cycle
137 days
Latest Release
510 days ago

Changelog History

  • v1.8 Changes

    May 24, 2020

    ๐Ÿ’… Upgrade pycodestyle and flake8 linter versions to support newer features

  • v1.7 Changes

    April 28, 2020
    • ๐Ÿš€ 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
  • v1.6 Changes

    March 16, 2019
    • ๐Ÿ‘ 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

  • v1.5 Changes

    March 08, 2019
    • ๐Ÿ’… 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
    • 0๏ธโƒฃ By default, only the diff in the PR will be scanned now. The earlier behaviour used to confuse new contributors. 1822b5d
    • ๐Ÿ›  Minor bug fixes
  • v1.4 Changes

    March 02, 2019
    • 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!

  • v1.3.2

    February 05, 2019
  • v1.3.1 Changes

    February 05, 2019
    • ๐Ÿ›  Fix a major bug in create_gist function #102 #103
  • v1.3 Changes

    February 20, 2017

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

    ๐Ÿ†• New Features

  • v1.2 Changes

    February 10, 2017

    New Features

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

    ๐Ÿ› Bug fixes

    ๐Ÿ‘Œ Improvements :

    • ๐Ÿ‘‰ Use the .pep8speaks.yml file from the PR.
  • v1.1.1 Changes

    January 06, 2017

    Bug fix :

    • Comment only if Python files are involved in the PR

    ๐Ÿ‘Œ Improvements :

    • Comment only if Python files are involved. So, install the integration on all of your repositories. The bot won't speak where it should not
    • ๐Ÿ‘Œ Improved comment body with appropriate hyperlinks to ease navigation
    • โž• Added all of pycodestyle configurations in .pep8speaks.yml
    • ๐Ÿ›ฐ Use a secret key for verifying payloads from GitHub
    • Less annoying

    ๐Ÿ†• New Features :

    • โœ… Mention @pep8speaks in a review summary while creating a review of a PR, and it will comment a gist of diff suggesting fixes for the PR. Example
      • In the review summary, you can also write @pep8speaks suggest diff or anything you wish, as long as you mention the bot.
    • ๐Ÿ’… Write @pep8speaks pep8ify in a review summary 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.
      • @pep8speaks along with pep8ify in a single review summary rules out the diff feature.