You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
488d34691a
When replicating to gitea from a remote system which makes use of git refs to store extra data (for example, gerrit), pushing a lot of refs to gitea can cause problems due to the extra processing that the pre and post receive hooks perform. But it's still useful for gitea to be able to serve those refs. This change skips unecessary processing of refs other than branches or tags. We don't need to check any ref that isn't a branch for branch protection (protection will never be enabled). So in the pre-receive hook, we wrap that check in a test for whether the ref is a branch. We also don't need to add information to the activity stream about pushes to non-standard refs, so we skip that step in the post-receive hook for refs which are not branches or tags. For some concrete examples, gerrit maintains a ref for every patchset of every change in the form refs/changes/XX/YYYY/Z. Many systems use refs/notes to store additonal data about commits. This change allows these and other schemes to be used without affecting gitea. |
5 years ago | |
|---|---|---|
| .. | ||
| admin.go | 5 years ago | |
| cert.go | 7 years ago | |
| cmd.go | 6 years ago | |
| dump.go | 5 years ago | |
| generate.go | 5 years ago | |
| hook.go | 5 years ago | |
| keys.go | 5 years ago | |
| migrate.go | 5 years ago | |
| serv.go | 5 years ago | |
| web.go | 5 years ago | |
| web_graceful.go | 5 years ago | |
| web_windows.go | 8 years ago | |