github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 10:39:38 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

[FR]: support for personal webhooks and site-wide webhooks #2064

New Issue
Closed
opened 2025-11-02 04:22:58 -06:00 by GiteaMirror · 11 comments
GiteaMirror commented 2025-11-02 04:22:58 -06:00
Owner
Copy Link

Originally created by @LER0ever on GitHub (Jul 17, 2018).

Feature Request: support for personal webhooks and site-wide webhooks

Description

Since most users host Gitea as their personal git server and frontend, It would be great if a user can have a personal webhook that triggers on every repository that belongs to him/her, that is username/*. It is also useful to have site-wide webhooks that react on all repos for those who want to do some "logging to slack" kinda stuff.

  • Gitea version (or commit ref): 7be5935
  • Git version: 2.18.0
  • Operating system: Manjaro Linux Latest
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:
Originally created by @LER0ever on GitHub (Jul 17, 2018). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> Feature Request: support for personal webhooks and site-wide webhooks ## Description Since most users host Gitea as their personal git server and frontend, It would be great if a user can have a personal webhook that triggers on every repository that belongs to him/her, that is `username/*`. It is also useful to have site-wide webhooks that react on all repos for those who want to do some "logging to slack" kinda stuff. - Gitea version (or commit ref): 7be5935 - Git version: 2.18.0 - Operating system: Manjaro Linux Latest - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist:
GiteaMirror added the type/proposaltype/feature labels 2025-11-02 04:22:58 -06:00
GiteaMirror commented 2025-11-02 04:22:59 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Jul 17, 2018):

Duplicate of #770

@techknowlogick commented on GitHub (Jul 17, 2018): Duplicate of #770
GiteaMirror commented 2025-11-02 04:22:59 -06:00
Author
Owner
Copy Link

@LER0ever commented on GitHub (Jul 17, 2018):

Hi @techknowlogick , I don't think it's a duplicate for #770
If I understand correctly, that issue allows to create a default set of webhooks when new repos are created, but that won't allow users to, let's say, create two webhooks, one to slack and one to discord, for all their repos. And since they are copied into new repos (#4299 ), batch changing them afterwards seems not possible.

@LER0ever commented on GitHub (Jul 17, 2018): Hi @techknowlogick , I don't think it's a duplicate for #770 If I understand correctly, that issue allows to create a default set of webhooks when new repos are created, but that won't allow users to, let's say, create two webhooks, one to slack and one to discord, for all their repos. And since they are copied into new repos (#4299 ), batch changing them afterwards seems not possible.
GiteaMirror commented 2025-11-02 04:22:59 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Jul 18, 2018):

@LER0ever thank you for clarifying. I've reopened this ticket.

@techknowlogick commented on GitHub (Jul 18, 2018): @LER0ever thank you for clarifying. I've reopened this ticket.
GiteaMirror commented 2025-11-02 04:22:59 -06:00
Author
Owner
Copy Link

@luismanolo commented on GitHub (Oct 4, 2018):

I like this proposal too...

@luismanolo commented on GitHub (Oct 4, 2018): I like this proposal too...
GiteaMirror commented 2025-11-02 04:23:00 -06:00
Author
Owner
Copy Link

@0x5c commented on GitHub (Feb 19, 2019):

Same as above, but I would add that having a trigger for mentions would be pretty nice

@0x5c commented on GitHub (Feb 19, 2019): Same as above, but I would add that having a trigger for mentions would be pretty nice
GiteaMirror commented 2025-11-02 04:23:00 -06:00
Author
Owner
Copy Link

@Mikaela commented on GitHub (Aug 16, 2019):

I was going to open a duplicate of this.

Feature request: user level webhooks

Description

Currently webhooks can only be set on individual repository and organisation level, while I wish I would be able to setup webhooks on user level applying to all of my repositories without having to visit their settings separately.

My usecase is a private IRC channel where I have feeds related to me and a IRC bot with support for Gitea. Currently I have to visit all repositories separately to configure webhooks (it's not a big problem as I don't have that many yet), but being able to configure them at one place would be easier.

I think noticing suspicious activity on my Gitea account could also be easier if I was informed about it all automatically.

Related: https://github.com/go-gitea/gitea/issues/7523 which requests system level global webhooks (later I guess that is a duplicate of this one)

@Mikaela commented on GitHub (Aug 16, 2019): I was going to open a duplicate of this. ## Feature request: user level webhooks - Gitea version (or commit ref): © Gitea Version: 1.10.0+dev-183-g867f46f78 - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (provide example URL) https://try.gitea.io/user/settings/hooks - 404 - [ ] No - [ ] Not relevant ## Description Currently webhooks can only be set on individual repository and organisation level, while I wish I would be able to setup webhooks on user level applying to all of my repositories without having to visit their settings separately. My usecase is a private IRC channel where I have feeds related to me and a IRC bot with support for Gitea. Currently I have to visit all repositories separately to configure webhooks (it's not a big problem as I don't have that many yet), but being able to configure them at one place would be easier. I think noticing suspicious activity on my Gitea account could also be easier if I was informed about it all automatically. Related: https://github.com/go-gitea/gitea/issues/7523 which requests system level global webhooks (later I guess that is a duplicate of this one)
GiteaMirror commented 2025-11-02 04:23:00 -06:00
Author
Owner
Copy Link

@0x5c commented on GitHub (Aug 17, 2019):

Would the best name for this be "notification webhooks"?

@0x5c commented on GitHub (Aug 17, 2019): Would the best name for this be "notification webhooks"?
GiteaMirror commented 2025-11-02 04:23:00 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Aug 17, 2019):

Notification is one of this, another maybe a backup, mirror or any other purpose.

@lunny commented on GitHub (Aug 17, 2019): Notification is one of this, another maybe a backup, mirror or any other purpose.
GiteaMirror commented 2025-11-02 04:23:01 -06:00
Author
Owner
Copy Link

@insertjokehere commented on GitHub (Sep 5, 2019):

My use case for this would be a "repo created" webhook that I could use to automatically configure some things (create jobs on my CI etc)

@insertjokehere commented on GitHub (Sep 5, 2019): My use case for this would be a "repo created" webhook that I could use to automatically configure some things (create jobs on my CI etc)
GiteaMirror commented 2025-11-02 04:23:01 -06:00
Author
Owner
Copy Link

@Mikaela commented on GitHub (Jan 16, 2022):

Another case for this would be Matrix webhooks being cumbersome to enable as they use the room ID

Matrix has room versions and to benefit from the features of the newer room versions a /upgraderoom is necessary. It then changes the room ID

And that means going through all webhooks and checking that they point to the new room instead of attempting to post into an old one

@Mikaela commented on GitHub (Jan 16, 2022): Another case for this would be Matrix webhooks being cumbersome to enable as they use the room ID Matrix has room versions and to benefit from the features of the newer room versions a `/upgraderoom` is necessary. It then changes the room ID And that means going through all webhooks and checking that they point to the new room instead of attempting to post into an old one
GiteaMirror commented 2025-11-02 04:23:01 -06:00
Author
Owner
Copy Link

@delvh commented on GitHub (Apr 29, 2023):

I remember a PR for system webhooks being merged.
I think that means this issue is closed, right?

@delvh commented on GitHub (Apr 29, 2023): I remember a PR for system webhooks being merged. I think that means this issue is closed, right?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/feature type/proposal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2064
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?