Mercurial > kallithea
diff README.rst @ 5452:c3d83238afa1
git: add option for forcing overwrite of Git hooks when remapping and rescanning the repositories. (Issue #153)
README file was updated to include some information on updating Git hooks after migrating to Kallithea.
author | Branko Majic <branko@majic.rs> |
---|---|
date | Tue, 01 Sep 2015 21:46:03 +0200 |
parents | fbbe80e3322b |
children | 57caeb60c52b |
line wrap: on
line diff
--- a/README.rst Wed Aug 26 17:28:59 2015 +0200 +++ b/README.rst Tue Sep 01 21:46:03 2015 +0200 @@ -201,6 +201,31 @@ If you started out using the branding interoperability approach mentioned above, watch out for stray brand.pyc after removing brand.py. +Git hooks +~~~~~~~~~ + +After switching to Kallithea, it will be necessary to update the Git_ hooks in +your repositories. If not, the Git_ hooks from RhodeCode will still be called, +which will cause ``git push`` to fail every time. + +If you do not have any custom Git_ hooks deployed, perform the following steps +(this may take some time depending on the number and size of repositories you +have): + +1. Log-in as an administrator. + +2. Open page *Admin > Settings > Remap and Rescan*. + +3. Turn on the option **Install Git Hooks**. + +4. Turn on the option **Overwrite existing Git hooks**. + +5. Click on the button **Rescan Repositories**. + +If you do have custom hooks, you will need to merge those changes manually. In +order to get sample hooks from Kallithea, the easiest way is to create a new Git_ +repository, and have a look at the hooks deployed there. + .. _virtualenv: http://pypi.python.org/pypi/virtualenv .. _Python: http://www.python.org/