Prevent pushing to master on GitHub?
GitHub allows you to configure your repository so that users can't force push to master, but is there a way to prevent pushing to master entirely? I'm hoping to make it so that the only way of adding to commits to master is through the GitHub pull request UI.
Since the original question / answer, Github has added a new option for this to the restricted branches UI which allows you to set this up.
Require pull request reviews before merging When enabled, all commits must be made to a non-protected branch and submitted via a pull request with the required number of approving reviews and no changes requested before it can be merged into a branch that matches this rule.
To find it go to Settings > Branches > Branch Protection Rules
and click 'Add Rule'.
Then, enter the name of the branch you want to protect.
Slightly below that, click the checkbox to "Require a pull request before merging"
By default, this only stops people who are not moderators. There is also another checkbox later down for ensuring that even moderators cannot merge, "Do not allow bypassing the above settings"
- Failed to connect to bitbucket.org port 443: Network is unreachable
- Where does Git store remote tracking branches
- IntelliJ: Viewing diff of all changed files between local and a git commit/branch
- Getting "fatal: bad revision" when trying to unsquash a commit in Git
- How to disable git pull.rebase (rebasing by default upon pull)
- File names only using Git grep
- What is the difference between git fetch and git fetch origin?
- How do I remove a submodule?
- error: failed to solve: failed commit on ref : unexpected status: 400 Bad Request
- Viewing full version tree in git
- How does git LFS track and store binary data more efficiently than git?
- How to prune local tracking branches that do not exist on remote anymore?
- jitpack.io failed to resolve github repo
- remote: Permission to repository denied. URL returned error: 403
- How to change current branch in git from master to main
- Which git environment variables (AUTHOR, COMMITTER) must be set so it represents the same config as `user.name` and `user.email`?
- How to git pull for multiple repos on windows?
- Git: Compare All Local Commits to Remote Repo Version
- How to prevent git asking me to commit submodule modifications
- How to list unpushed Git commits (local but not on origin)
- Can you easily spread Git remote url changes to all developers?
- Find which commit is currently checked out in Git
- Finding what checkin broke a unit test
- How can I perform a Git bisect if I don't know which old commit is good?
- Why did my Git repo enter a detached HEAD state?
- How do you reset the stored credentials in 'git credential-osxkeychain'?
- How can I Git bisect where a bad commit is an ancestor of a good commit / find the fix commit?
- How can I find the commit in which a given file was added?
- bisect everything, from initial commit
- How can I find out what commit(s) Git bisect would try next?