Branch Protection Rule #74
healtheloper
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Branch Name Pattern
[dm][ea][vs]*
Protect matching branches
Merge 하기 전 Pull Request 필요 - Require a pull request before merging
When enabled, all commits must be made to a non-protected branch and submitted via a pull request before they can be merged into a branch that matches this rule.
When enabled, pull requests targeting a matching branch require a number of approvals and no changes requested before they can be merged.
2
New reviewable commits pushed to a matching branch will dismiss pull request review approvals. (22.11.24 잠시 해지)
Require an approved review in pull requests including files with a designated code owner.
Specify people, teams, or apps allowed to dismiss pull request reviews.
Specify people, teams, or apps who are allowed to bypass required pull requests.
Require review approval from someone other than the last pusher to the pull request branch.
모든 Status Checks 가 Pass - Require status checks to pass before merging
Choose which status checks must pass before branches can be merged into a branch that matches this rule. When enabled, commits must first be pushed to another branch, then merged or pushed directly to a branch that matches this rule after status checks have passed.
This ensures pull requests targeting a matching branch have been tested with the latest code. This setting will not take effect unless at least one status check is enabled (see below).
Require conversation resolution before merging
When enabled, all conversations on code must be resolved before a pull request can be merged into a branch that matches this rule. Learn more.
Require signed commits
Commits pushed to matching branches must have verified signatures.
Require linear history
Prevent merge commits from being pushed to matching branches.
Enable squashing or rebasing merge strategy on this repository to use this rule.
Require deployments to succeed before merging
Choose which environments must be successfully deployed to before branches can be merged into a branch that matches this rule.
Lock branch
Branch is read-only. Users cannot push to the branch.
Protection rule 무시하는 것을 허용하지 않음 - Do not allow bypassing the above settings
The above settings will apply to administrators and custom roles with the "bypass branch protections" permission.
Restrict who can push to matching branches
Specify people, teams, or apps allowed to push to matching branches. Required status checks will still prevent these people, teams, and apps from merging if the checks fail.
Rules applied to everyone including administrators
Allow force pushes
Permit force pushes for all users with push access.
Allow deletions
Allow users with push access to delete matching branches.
Beta Was this translation helpful? Give feedback.
All reactions