summaryrefslogtreecommitdiff
path: root/hooks/post-receive
Commit message (Collapse)AuthorAgeFilesLines
* Revert "Merge branch 'sh-disable-rubygems' into 'master'"Stan Hu2017-07-051-1/+1
| | | | | This reverts commit a18c90128e4d3eeae1233b1bc3c3998afd223c0d, reversing changes made to 0a64624152735766c428d1532e434dd0bf5a9748.
* Disable Rubygems in hooks toosh-disable-rubygemsStan Hu2017-07-041-1/+1
|
* Handle GL_REPOSITORY env variable and use it in api callsAlejandro Rodríguez2017-05-111-1/+2
|
* remove no longer needed gitlab_initElan Ruusamäe2016-12-011-1/+0
|
* custom_hook: add support for global custom hooksDirk Hörner2016-12-011-0/+1
| | | | | | | | | | | | | This commit adds the option of having another set of global custom hooks along with the already supported repository local custom hooks. The repository local custom hook is executed first (if available). If successful, execution continues with the global custom hook (if available). This way, local custom hooks get priority over global custom hooks. Global custom hooks can be enabled by placing an executable file into the "custom_hooks" directory within gitlab-shell (create if it does not exist, yet).
* custom_hook: refactor to pull repo_path into classDirk Hörner2016-12-011-1/+1
| | | | | | This commit takes the GitlabCustomHook a bit clother to the other hook handling classes by receiving the repo_path as argument to initialize() instead of passing it to each method.
* added GL_IDadd_gl_idValery Sizov2016-10-051-1/+1
|
* Unset GL_ID and GL_PROTOCOL immediatelyJacob Vosmaer2016-07-201-4/+1
| | | | | | Neither other code executing in the hook process nor subprocesses of the hook process need access to the GL_ID / GL_PROTOCOL variables so we can just unset them the moment we fetch them.
* ARGF does more than we wantJacob Vosmaer2016-06-231-1/+1
| | | | | | | | | ARGF is a virtual IO stream that treats the elements of ARGV as paths to files to be opened. In practice, git-receive-pack will probably never pass arguments to pre-receive and post-receive because it is not supposed to (according to 'man 5 githooks'). In case it does, however our hooks should not have the surprise behavior of treating those arguments as files to be opened.
* Move setting/unsetting of GL_ID from lib to executables.Douwe Maan2015-04-061-0/+3
|
* Revert "Restore hooks PATH before calling ruby."Valery Sizov2014-11-191-4/+17
| | | | This reverts commit cd9e796316560eee596f2681d54a8417389bbe79.
* Restore hooks PATH before calling ruby.Ciro Santilli2014-11-171-17/+4
|
* Support for custom hooksDrew Blessing2014-11-051-3/+4
|
* Add new pre-receive and post-receive hooksDmitriy Zaporozhets2014-09-011-0/+17
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Remove empty post-receive hookJacob Vosmaer2013-07-191-4/+0
|
* Mention that users can edit the hooksJacob Vosmaer2013-07-191-3/+1
|
* Use update hook to add post event to redis. Use GL_ID instead of GL_USERDmitriy Zaporozhets2013-02-141-9/+4
|
* Update hook and support for protected branchesDmitriy Zaporozhets2013-02-061-1/+0
|
* set GL_USERDmitriy Zaporozhets2013-02-041-0/+0
|
* link post-receive hook alsoDmitriy Zaporozhets2013-02-041-0/+12
View Lorry Controller Status