You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our team uses pre-commit to ensure certain tests pass before committing the changes. However, in some cases, it's unnecessary to run these scripts(e.g. when editing README.md) and so we're able to skip them by appending the --no-verify param to the command.
Example
git commit -m "John Doe" --no-verify
What's your opinion on this feature? Can you see any security issue?
The text was updated successfully, but these errors were encountered:
This would give consumers of the Action more control.
We can append the options at the end of the git-commit line here.
Can you see any security issue?
No, not really. The Action "just" creates a new commit.
However, if you have some critical checks in your pre-commit-settings and you decided to ignore those with --no-verify and something bad happens … that's a decision the user made 🤷♂.
However, if you have some critical checks in your pre-commit-settings and you decided to ignore those with --no-verify and something bad happens … that's a decision the user made 🤷♂.
Yes, that's rather sort of a responsibility on the user's side to control the arguments passed into the command.
Thanks for the quick feedback and suggestions, I'll submit a PR soon.
Our team uses
pre-commit
to ensure certain tests pass before committing the changes. However, in some cases, it's unnecessary to run these scripts(e.g. when editingREADME.md
) and so we're able to skip them by appending the--no-verify
param to the command.Example
git commit -m "John Doe" --no-verify
What's your opinion on this feature? Can you see any security issue?
The text was updated successfully, but these errors were encountered: