You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Follows
#21129 (comment)
* #21129 (comment)
A lot of users are asking similar questions.
The old content in FAQ doesn't seem to be related to the problem.
Copy file name to clipboardExpand all lines: docs/content/doc/help/faq.en-us.md
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -214,13 +214,13 @@ Our translations are currently crowd-sourced on our [Crowdin project](https://cr
214
214
215
215
Whether you want to change a translation or add a new one, it will need to be there as all translations are overwritten in our CI via the Crowdin integration.
216
216
217
-
## Hooks aren't running
217
+
## Push Hook / Webhook aren't running
218
218
219
-
If Gitea is not running hooks, a common cause is incorrect setup of SSH keys.
219
+
If you can push but can't see push activities on the home dashboard, or the push doesn't trigger webhook, there are a few possibilities:
220
220
221
-
See [SSH Issues](#ssh-issues) for more information.
222
-
223
-
You can also try logging into the administration panel and running the `Resynchronize pre-receive, update and post-receive hooks of all repositories.` option.
221
+
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
222
+
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`
223
+
3. If you are using docker, make sure Docker Server (not the client) >= 20.10.6
0 commit comments