Skip to content
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

Closed
2 of 7 tasks
LER0ever opened this issue Jul 17, 2018 · 11 comments
Closed
2 of 7 tasks

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

LER0ever opened this issue Jul 17, 2018 · 11 comments
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@LER0ever
Copy link
Contributor

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:
@techknowlogick
Copy link
Member

Duplicate of #770

@techknowlogick techknowlogick marked this as a duplicate of #770 Jul 17, 2018
@techknowlogick techknowlogick added the issue/duplicate The issue has already been reported. label Jul 17, 2018
@LER0ever
Copy link
Contributor Author

LER0ever commented 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.

@techknowlogick techknowlogick added type/feature Completely new functionality. Can only be merged if feature freeze is not active. and removed issue/duplicate The issue has already been reported. labels Jul 18, 2018
@techknowlogick
Copy link
Member

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

@techknowlogick techknowlogick added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Jul 18, 2018
@luismanolo
Copy link

I like this proposal too...

@0x5c
Copy link
Contributor

0x5c commented Feb 19, 2019

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

@Mikaela
Copy link
Contributor

Mikaela commented 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: #7523 which requests system level global webhooks (later I guess that is a duplicate of this one)

@0x5c
Copy link
Contributor

0x5c commented Aug 17, 2019

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

@lunny
Copy link
Member

lunny commented Aug 17, 2019

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

@insertjokehere
Copy link

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)

@Mikaela
Copy link
Contributor

Mikaela commented 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

@delvh
Copy link
Member

delvh commented Apr 29, 2023

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

@delvh delvh closed this as completed Apr 29, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 14, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

No branches or pull requests

8 participants