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.

Sign up for GitHub

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

Jump to bottom

Fix readme to correctly reflect no-commit-to-branch args #318

Merged
merged 2 commits into from
Oct 10, 2018
Merged

Fix readme to correctly reflect no-commit-to-branch args #318

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
023851e
Fix readme to correctly reflect no-commit-to-branch args
milind-shakya-sp Oct 4, 2018
3aa6c64
Update README.md
asottile Oct 10, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,7 +82,7 @@ Add this to your `.pre-commit-config.yaml`
- `name-tests-test` - Assert that files in tests/ end in `_test.py`.
- Use `args: ['--django']` to match `test*.py` instead.
- `no-commit-to-branch` - Protect specific branches from direct checkins.
- Use `args: [--branch <branch>]` to set the branch. `master` is the
- Use `args: ['staging', 'master']` to set the branch. `master` is the
Copy link
Member

Choose a reason for hiding this comment

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

ah yeah this would be args: [--branch, staging, --branch, master] -- good catch!

default if no argument is set.
- `-b` / `--branch` may be specified multiple times to protect multiple
branches.
Expand Down