prevent `git` from pushing commits with given commit message

How to prevent git from pushing commits that contain given string in commit massage, e.g. “DO NOT PUSH” ?


  • GIT un-rollback a commit
  • Git: how to ignore hidden files / dot files / files with empty file names via .gitignore?
  • git pre-receive hook - getting the newest code
  • Deploy and build my go app on my server
  • How to check if git merge problems have been fixed?
  • Caching functions in Python to disk with expiration based on version
  • My typical workflow is:
    I hack hack, splitting work into micro commits,
    once things work I rewrite history, changing order of commit to group them reasonably and later squashing into bigger meaningful pieces.
    Once work is ready, things are ready to push!

    Now I would like git to prevent me from accidentally pushing into repository commits that are still in progress.
    I considered keeping “DO NOT PUSH” as part of commit message.
    How to make git automatically prevent me from pushing when it reaches such commit after git push?

    (On for pre-receive hook solutions: let’s consider github as example service, which AFAIK does not allow pre-recevie hooks, except in its “Enterprise” edition)

  • How do I get a “git log” patch for a specific commit
  • Create branch in remote repository without having local repository
  • Single file as Git submodule
  • Is there a way to use a Mercurial repository as Git submodule?
  • How can I check in a bash script if my local git repo has changes
  • git fetch origin doesn't fetch all branches
  • One Solution collect form web for “prevent `git` from pushing commits with given commit message”

    You can use a pre-push hook, but that remains a local hook which can be bypassed.
    See this pre-push example which does look at each commit message

    # Check for foo commit
            commit=`git rev-list -n 1 --grep '^foo' "$range"`
            if [ -n "$commit" ]
    echo "ERROR: git pre-push hook found commit message starting with 'foo' in $local_ref"

    But the best way remains a pre-receive hook on the server side though. That way, the policy is enforced for all contributors. This is not always possible (when you don’t have direct access to the remote server like GitHub, BitBucket or

    Git Baby is a git and github fan, let's start git clone.