From 57ee3a4653cee04a828c5550d1e86faf4b9d961b Mon Sep 17 00:00:00 2001 From: vmmello Date: Mon, 23 Dec 2024 03:44:44 +0000 Subject: [PATCH] FAQ: improves answer of question "Push Hook / Webhook / Actions aren't running" (#130) On FAQ item: "Push Hook / Webhook / Actions aren't running" The action suggested in the original answer is not enough to fix the issue when the hooks are not running. For example, when none of the hooks is running, and branches and tags are not in the database, re-running only the update/receive hooks will not have any effect. This change adds two additional actions: sync branches and tags before running re-running the sync of update/receive hooks. Also added a comment about filesystems mounted with `no-exec` option. Co-authored-by: Lunny Xiao Reviewed-on: https://gitea.com/gitea/docs/pulls/130 Reviewed-by: Lunny Xiao Co-authored-by: vmmello Co-committed-by: vmmello --- docs/help/faq.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/help/faq.md b/docs/help/faq.md index 76017b45..c763fe9b 100644 --- a/docs/help/faq.md +++ b/docs/help/faq.md @@ -184,8 +184,11 @@ If you can push but can't see push activities on the home dashboard, or the push There are a few possibilities: -1. The git hooks are out of sync: run "Resynchronize pre-receive, update and post-receive hooks of all repositories" on the site admin panel -2. The git repositories (and hooks) are stored on some filesystems (ex: mounted by NAS) which don't support script execution, make sure the filesystem supports `chmod a+x any-script` +1. The git hooks are out of sync. Run the following actions on the site admin panel: +- "Sync missed branches from git data to databases" +- "Sync tags from git data to database" +- "Resynchronize pre-receive, update and post-receive hooks of all repositories" +2. The git repositories (and hooks) are stored on some filesystems (ex: mounted by NAS) which don't support script execution, make sure the filesystem supports `chmod a+x any-script`. Also make sure that the filesystem of the repositories is not mounted with the `noexec` option. 3. If you are using docker, make sure Docker Server (not the client) >= 20.10.6 ## SSH issues