Replies: 3 comments
-
Did you replace the
|
Beta Was this translation helpful? Give feedback.
0 replies
-
You should only need a |
Beta Was this translation helpful? Give feedback.
0 replies
-
I did, but we use ssh, so the link is a 'git@' rather than 'https://' link. I
guess that's the problem. Thanks for pointing that out. I'll see if I can
work around it.
…On Fri, May 6, 2022, 2:41 AM Michal Porteš ***@***.***> wrote:
Did you replace the '' # Update me! part with an actual revision (tag,
branch or commit)? For example:
repos:
- repo: https://github.com/PyCQA/bandit
rev: 1.7.4
hooks:
- id: bandit
—
Reply to this email directly, view it on GitHub
<#895 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA7H32OX3BG4KEGOY5I4HFDVITELPANCNFSM5VGPZ5SA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I followed the instructions at https://bandit.readthedocs.io/en/latest/start.html#version-control-integration, but when I attempt to commit a change, I receive the error ".../.pre-commit-hooks.yaml is not a file". The pre-commit doc says "A git repo containing pre-commit plugins must contain a .pre-commit-hooks.yaml file". Did I miss a step that should have generated this file or is this a manual step missing from the Bandit doc that I need to perform manually? I apologize if this is a dumb question, but I am new to both Bandit and pre-commit.
Beta Was this translation helpful? Give feedback.
All reactions