Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add pre-commit config #411

Merged
merged 1 commit into from Oct 29, 2018

Conversation

KPilnacek
Copy link

Resolving: #410

Copy link
Member

@asottile asottile left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lg2m

@@ -0,0 +1,6 @@
- id: bandit
name: bandit
description: 'Bandit a tool for finding common security issues in Python code'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Bandit is a tool"

@KPilnacek
Copy link
Author

fixed

@lukehinds lukehinds merged commit 8f4c216 into PyCQA:master Oct 29, 2018
asottile added a commit to pre-commit/pre-commit.com that referenced this pull request Oct 29, 2018
@ericwb ericwb mentioned this pull request Nov 12, 2018
@espoelstra
Copy link

It would be great if a release could be tagged with this functionality, it took me a while to figure out that I couldn't use 1.5.1 as the rev/tag for bandit in pre-commit, I had to use master or anything after the merge of this PR. Using release tags also allows pre-commit autoupdate to automatically grab newer versions of bandit for users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants