This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
git_hooks [2017/12/20 01:15] – [How it works] admin | git_hooks [2017/12/20 01:34] (current) – admin | ||
---|---|---|---|
Line 3: | Line 3: | ||
===== pre-receive Hook (Server-Side) ===== | ===== pre-receive Hook (Server-Side) ===== | ||
- | This is a hook i use along with Gitlab. Its global and will be triggerd for all repositories when data ist send to the server. | + | This is a hook i use along with Gitlab. Its global and will be triggerd for all repositories when data is send to the server. When data is send to the server old and new revs will be compared depending on the changed files. If the changed files contain a file named < |
+ | |||
+ | In case **WHAT-EVER-YOUR-BRANCH-IS** is equal to the branch you try to push to the merge will not be refuse. This is because we want to be able to create the .do_not_merge file where necessary. | ||
==== Setup ==== | ==== Setup ==== | ||
Line 17: | Line 19: | ||
Make sure **THE-BRANCH-NAME** its exactly the same name as the Branch. | Make sure **THE-BRANCH-NAME** its exactly the same name as the Branch. | ||
- | Given you have the branch '' | + | Given you have the branch '' |
+ | ==== Expected output in CLI ==== | ||
+ | |||
+ | {{:: | ||
==== The Hook ==== | ==== The Hook ==== | ||
Line 107: | Line 112: | ||
end | end | ||
end </ | end </ | ||
+ | |||
+ | ==== ToDo ==== | ||
+ | |||
+ | * Find a way to make hook output look pretty in Gitlab {{:: | ||