-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FR]: support for personal webhooks and site-wide webhooks #4456
Comments
Duplicate of #770 |
Hi @techknowlogick , I don't think it's a duplicate for #770 |
@LER0ever thank you for clarifying. I've reopened this ticket. |
I like this proposal too... |
Same as above, but I would add that having a trigger for mentions would be pretty nice |
I was going to open a duplicate of this. Feature request: user level webhooks
DescriptionCurrently 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: #7523 which requests system level global webhooks (later I guess that is a duplicate of this one) |
Would the best name for this be "notification webhooks"? |
Notification is one of this, another maybe a backup, mirror or any other purpose. |
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) |
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 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 |
I remember a PR for system webhooks being merged. |
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.[x]
):The text was updated successfully, but these errors were encountered: