Allow adding a default set of githooks and webhooks #291

New Issue

GiteaMirror · 2025-11-02T03:17:29-06:00

GiteaMirror commented

2025-11-02 03:17:29 -06:00

Originally created by @alvaroaleman on GitHub (Jan 26, 2017).

It would be nice if it was possible to configure a default set of githooks and webhooks in the admin interface and/or at organization level.

That default set should then be applied to all newly created repositories. It should also be possible to use the repository name as variable.

Originally created by @alvaroaleman on GitHub (Jan 26, 2017). It would be nice if it was possible to configure a default set of githooks and webhooks in the admin interface and/or at organization level. That default set should then be applied to all newly created repositories. It should also be possible to use the repository name as variable.

GiteaMirror added the issue/confirmed type/feature labels 2025-11-02 03:17:29 -06:00

GiteaMirror closed this issue

2025-11-02 03:17:29 -06:00

GiteaMirror commented

2025-11-02 03:17:30 -06:00

@charlesreid1 commented on GitHub (Apr 10, 2018):

Agreed! This would also make it much simpler to set up a static page hosting service, Github Pages style. You can create a webhook that triggers a site builder on commit to a particular branch, and have it installed on all pages by default.

@charlesreid1 commented on GitHub (Apr 10, 2018): Agreed! This would also make it much simpler to set up a static page hosting service, Github Pages style. You can create a webhook that triggers a site builder on commit to a particular branch, and have it installed on all pages by default.

GiteaMirror commented

2025-11-02 03:17:30 -06:00

@aunger commented on GitHub (Jun 19, 2018):

I'm going to take a crack at this, but I'd like some design feedback on the question of default vs all.

For my purposes, adding an admin set of web hooks for all repos would be sufficient. These would be invisible to the individual org and repo settings pages, and could only be altered by admin. As the administrator of the system, I want my own set of hooks to fire upon pushes, for example.

As I understand #770, it requests default webhooks instead, which are copied into new orgs and new repos, and may then be altered or deleted by the org/repo owner. This could work for my needs, too.

I can implement whichever is more likely to be merged. Thanks! Thoughts?

@aunger commented on GitHub (Jun 19, 2018): I'm going to take a crack at this, but I'd like some design feedback on the question of **default** vs **all**. For my purposes, adding an admin set of web hooks for **all repos** would be sufficient. These would be invisible to the individual org and repo settings pages, and could only be altered by admin. As the administrator of the system, I want my own set of hooks to fire upon pushes, for example. As I understand #770, it requests **default** webhooks instead, which are copied into new orgs and new repos, and may then be altered or deleted by the org/repo owner. This could work for my needs, too. I can implement whichever is more likely to be merged. Thanks! Thoughts?

GiteaMirror commented

2025-11-02 03:17:30 -06:00

@stale[bot] commented on GitHub (Jan 23, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 23, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 03:17:30 -06:00

@techknowlogick commented on GitHub (Mar 19, 2019):

Closed per merged PR

@techknowlogick commented on GitHub (Mar 19, 2019): Closed per merged PR

GiteaMirror referenced this issue

2025-11-02 11:43:13 -06:00

[PR #291] [MERGED] Golint fixed for models/migrations #15289

Sign in to join this conversation.