realaravinth/forgejo-federation
1
0
Fork 0
Code Issues Pull requests 6 Projects Releases Packages Wiki Activity

Fix the hook related FAQ contents (#21297)

Browse source 
Follows
https://github.com/go-gitea/gitea/issues/21129#issuecomment-1260802986
* https://github.com/go-gitea/gitea/issues/21129#issuecomment-1260802986

A lot of users are asking similar questions.

The old content in FAQ doesn't seem to be related to the problem.
This commit is contained in:
wxiaoguang 2022-09-30 01:20:22 +08:00 committed by GitHub
parent 1d3095b718
commit 3b6a7e5c8a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
docs/content/doc/help/faq.en-us.md
View file

@ -214,13 +214,13 @@ Our translations are currently crowd-sourced on our [Crowdin project](https://cr
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. 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.
## Hooks aren't running ## Push Hook / Webhook aren't running
If Gitea is not running hooks, a common cause is incorrect setup of SSH keys. 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:
See [SSH Issues](#ssh-issues) for more information. 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`
You can also try logging into the administration panel and running the `Resynchronize pre-receive, update and post-receive hooks of all repositories.` option. 3. If you are using docker, make sure Docker Server (not the client) >= 20.10.6
## SSH issues ## SSH issues