Skip to content

WebHooks: branch filter for push/pull request notifications #2025

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
Avalancs opened this issue Jun 21, 2017 · 3 comments · Fixed by #7791
Closed

WebHooks: branch filter for push/pull request notifications #2025

Avalancs opened this issue Jun 21, 2017 · 3 comments · Fixed by #7791
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.
Milestone

Comments

@Avalancs
Copy link

I would like to notify Jenkins when there is a new push, or accepted pull request to the master branch, so it can be built and deployed for testing.
I could trigger the build without the use of the Gogs webhook plugin but the webhook is triggered for any pushes to the repository, not just the master branch.
So I would like to request the ability to create a filter for which branches a webhook should activate.

@lunny lunny added 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. labels Jun 21, 2017
@lunny lunny added this to the 1.x.x milestone Jun 21, 2017
@kmadel
Copy link
Contributor

kmadel commented Jun 25, 2017

Perhaps a Gitea Pipeline Multi-branch plugin for Jenkins. So filter from the Jenkins side, rather than the Gitea side. Although that is an interesting concept and one I don't believe GitHub supports.

@lafriks
Copy link
Member

lafriks commented Jun 25, 2017

I think it should be done on gitea side as I would also like to get slack/mattermost notifications only for specific branches

1 similar comment
@lafriks
Copy link
Member

lafriks commented Jun 25, 2017

I think it should be done on gitea side as I would also like to get slack/mattermost notifications only for specific branches

@lunny lunny mentioned this issue Aug 29, 2017
6 tasks
@lunny lunny mentioned this issue May 21, 2018
7 tasks
WGH- added a commit to WGH-/gitea that referenced this issue Aug 8, 2019
WGH- added a commit to WGH-/gitea that referenced this issue Sep 4, 2019
lafriks pushed a commit that referenced this issue Sep 9, 2019
* Fix validate() function to handle errors in embedded anon structs

* Implement webhook branch filter

See #2025, #3998.
@lunny lunny modified the milestones: 1.x.x, 1.10.0 Sep 12, 2019
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
# for free to subscribe to this conversation on GitHub. Already have an account? #.
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

Successfully merging a pull request may close this issue.

4 participants