Prevent commits in master branch

by

Yes, it is possible. You must create a pre-commit hook which rejects commits to the master branch. Git doesn’t call a pre-commit hook when you call the merge command, so this hook will be rejecting only regular commits.

  1. Go to your repository.

  2. Create a file, .git/hooks/pre-commit, with the following content:

    #!/bin/sh

branch="$(git rev-parse --abbrev-ref HEAD)"

if [ "$branch" = "master" ]; then
  echo "You can't commit directly to master branch"
  exit 1
fi

  3. Make it executable (not required on Windows):

    chmod +x .git/hooks/pre-commit

To disable fast-forward merges, you must also add the following option to your .git/config file:

[branch "master"]
    mergeoptions = --no-ff

If you want also protect the master branch on your remote, check this answer: How to restrict access to master branch in Git

More Related Contents:

  1. What effect does the `–no-ff` flag have for `git merge`?
  2. Can I make fast forwarding be off by default in git?
  3. Evil merges in git?
  4. What is the difference between merge –squash and rebase?
  5. When would you use the different git merge strategies?
  6. What’s the difference between ‘git merge’ and ‘git rebase’?
  7. Git – how to force merge conflict and manual merge on selected file
  8. Is it possible for git-merge to ignore line-ending differences?
  9. What’s the best visual merge tool for Git? [closed]
  10. Git: ignore some files during a merge (keep some files restricted to one branch)
  11. Moving Git repository content to another repository preserving history
  12. Git merge reports “Already up-to-date” though there is a difference
  13. Rebasing a Git merge commit
  14. How do I merge changes to a single file, rather than merging commits?
  15. How does ‘git merge’ work in details?
  16. Merge changes from remote github repository to your local repository
  17. Pull a certain branch from the remote server
  18. How to “git show” a merge commit with combined diff output even when every changed file agrees with one of the parents?
  19. How do I use `git rebase -i` after `git merge` without messing things up?
  20. git partial merge, not whole branch
  21. How to identify conflicting commits by hash during git rebase?
  22. What Git branching models work for you?
  23. How to merge two branches without a common ancestor?
  24. Git – how to force manual merge even if there is no conflict
  25. How to rebase one Git repository onto another one?
  26. Tell git not to merge binary files but to choose
  27. git: merge two branches: what direction?
  28. Git merge squash repeatedly
  29. git merging branches in a bare repository
  30. The following untracked working tree files would be overwritten by merge, but I don’t care

Leave a Comment