Skip to content

Commit 52e51fe

Browse files
committed
Activate PEP8 Speaks
1 parent 9fded27 commit 52e51fe

File tree

1 file changed

+26
-0
lines changed

1 file changed

+26
-0
lines changed

.pep8speaks.yml

+26
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
scanner:
2+
diff_only: True # If False, the entire file touched by the Pull Request is scanned for errors. If True, only the diff is scanned.
3+
linter: pycodestyle # Other option is flake8
4+
5+
pycodestyle: # Same as scanner.linter value. Other option is flake8
6+
max-line-length: 100 # Default is 79 in PEP 8
7+
ignore: # Errors and warnings to ignore
8+
- W504 # line break after binary operator
9+
- E402 # module level import not at top of file
10+
- E731 # do not assign a lambda expression, use a def
11+
- C406 # Unnecessary list literal - rewrite as a dict literal.
12+
- E741 # ambiguous variable name
13+
14+
no_blank_comment: True # If True, no comment is made on PR without any errors.
15+
descending_issues_order: False # If True, PEP 8 issues in message will be displayed in descending order of line numbers in the file
16+
17+
message: # Customize the comment made by the bot
18+
opened: # Messages when a new PR is submitted
19+
header: "Hello @{name}! Thanks for opening this PR. "
20+
# The keyword {name} is converted into the author's username
21+
footer: "Do see the [Hitchhiker's guide to code style](https://goo.gl/hqbW4r)"
22+
# The messages can be written as they would over GitHub
23+
updated: # Messages when new commits are added to the PR
24+
header: "Hello @{name}! Thanks for updating this PR. "
25+
footer: "" # Why to comment the link to the style guide everytime? :)
26+
no_errors: "There are currently no PEP 8 issues detected in this Pull Request. Cheers! :beers: "

0 commit comments

Comments
 (0)