Should all of them be combined into one single large pre-commit script ? Yes and no: you can only declare one pre-commit script, so this script should be in charge to: call the actual pre-commit scripts chose an order for those scripts to be called. So: one pre-commit script calling multiple scripts, each one allowing … Read more
Since powershell 7.2 the script must have .ps1 extension on Windows. So this answer will not work. You can embed PowerShell script directly inside the hook file. Here is an example of a pre-commit hook I’ve used: #!/usr/bin/env pwsh # Verify user’s Git config has appropriate email address if ($env:GIT_AUTHOR_EMAIL -notmatch ‘@(non\.)?acme\.com$’) { Write-Warning “Your … Read more
Name your hook pre-commit (without any file extension). And add #!/bin/sh on the first line or #!/bin/bash.
A git hook is a script placed in a special location of your repository, that location is: .git/hooks The script can be any kind that you can execute in your environment i.e. bash, python, ruby etc. The hook that is executed after a checkout is post-checkout. From the docs: …The hook is given three parameters… … Read more
I’ll leave this here as an answer because I stumbled upon my own answer for when my post-commit hook wasn’t running: chmod +x .git/hooks/post-commit Probably applies to any kind of hook. In fact, probably applies to any kind of script.
You can try using the prepare-commit-msg hook. The second argument will be merge “if the commit is a merge or a .git/MERGE_MSG file exists”. A non-zero exit status will abort the commit. I don’t think this will work with a fast-forward merge, since there won’t be a commit message. More info on hooks: https://www.kernel.org/pub/software/scm/git/docs/githooks.html#_prepare_commit_msg
Note: These messages can be disabled now. See Jake’s answer. Read along my answer for the technical explanation. Everything that is prefixed by remote: has been sent by the receiving script1 on the server. Bitbucket probably wants to make it easier for you to create a pull request. 1 Example of such a post-receive hook … Read more
Another solution to this problem is to have a wrapper for git push that executes .git/hooks/pre-push and .git/hooks/post-push scripts before and after the git push call. A possible wrapper could look like this: #!/bin/sh GIT_DIR_=”$(git rev-parse –git-dir)” BRANCH=”$(git rev-parse –symbolic –abbrev-ref $(git symbolic-ref HEAD))” PRE_PUSH=”$GIT_DIR_/hooks/pre-push” POST_PUSH=”$GIT_DIR_/hooks/post-push” test -x “$PRE_PUSH” && exec “$PRE_PUSH” “$BRANCH” “$@” git … Read more
http://benjamin-meyer.blogspot.com/2008/10/git-hooks.html Files in the .git/hooks directory are not part of the repository and so they are not tracked. A workaround is to have a git_hooks directory at the top of your repository like done in Arora and symlink .git/hooks to git_hooks whenever you clone. This way the hooks will be part of the project, under … Read more
No chance, if file is not mergeable and you need to lock it, use a centralized solution instead of GIT, i.e. SVN or ClearCase.