| commit | 41c3ad1d584f3b81bacc59e89e022dc1e7ffc3f2 | [log] [tgz] |
|---|---|---|
| author | Saša Živkov <sasa.zivkov@sap.com> | Fri Apr 05 17:32:14 2024 +0200 |
| committer | Saša Živkov <sasa.zivkov@sap.com> | Fri Apr 05 17:36:39 2024 +0200 |
| tree | febd7ee67889ef5714c4cf930e32cc2a4c636dd3 | |
| parent | f975f914312b258f84957d19f96014c3edd12644 [diff] |
Resolve relative hooks.path against $site_path, not cwd of the process When hooks.path was given as relative path it got resolved against the current working directory of the Gerrit process. While it may often be the case that the current working directory of Gerrit process is the $site_path, it is not guaranteed and, depending how Gerrit is started, it may be some other directory. Most, if not all, of the relative paths in gerrit.config are resolved against the $site_path and we should do the same for the hooks.path. Release-Notes: Resolve relative hooks.path against $site_path Change-Id: Ie72c0657393e1dfe078155e27edbd4c0412892e6
Gerrit does not support the standard server-side git hooks in the repositories it manages.
This plugin adds support for custom hooks that can be run instead. Refer to the configuration documentation and list of supported hooks for details.