From 8b54b58bc589d501c3459f1dbf8ba0b564cdc4e0 Mon Sep 17 00:00:00 2001 From: W Anders Date: Sat, 14 Sep 2019 21:37:09 -0500 Subject: [PATCH] Include git-hook regeneration in restore documentation (#8181) * Added admin cmd ref to backup-restore guide * Clarified reason for command execution * Include directive for where command should be executed from Co-Authored-By: guillep2k <18600385+guillep2k@users.noreply.github.com> * Be direct in consequences Co-Authored-By: guillep2k <18600385+guillep2k@users.noreply.github.com> --- docs/content/doc/usage/backup-and-restore.en-us.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/content/doc/usage/backup-and-restore.en-us.md b/docs/content/doc/usage/backup-and-restore.en-us.md index 5cf2f4aec..a3887bc64 100644 --- a/docs/content/doc/usage/backup-and-restore.en-us.md +++ b/docs/content/doc/usage/backup-and-restore.en-us.md @@ -79,3 +79,9 @@ mysql -u$USER -p$PASS $DATABASE Docker), or if Gitea is installed to a different directory than the previous installation. + +With Gitea running, and from the directory Gitea's binary is located, execute: `./gitea admin regenerate hooks` + +This ensures that application and configuration file paths in repository git-hooks are consistent and applicable to the current installation. If these paths are not updated, repository `push` actions will fail.