-
-
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
PUSH event hooks not sent for branch removal #2105
Comments
Could you include the logs from gitea? without them it's very hard to see what's happening :) |
(Not sure if this is bug or not, might be a feature request 😅 ) |
I'll see if I can dig it out but your Jenkins integration (which I have nearly finished) will be annoying without an event for this. If you want feature requests:
Icing on top:
|
Logs Creating the branch: (
Now the log when deleting the branch (
No events in the UI, no events in request bin @bkcsoft does that help? |
Says "git push to a repository" so should be all git pushes, even those that remove refs. That's a bug if you ask me. A feature would be a separate new event for "delete" but the "push" should include removal based on its description |
Just says This is clearly a bug |
If you want to have a new event for non-push that is a delete event, that would be a separate feature request, but this issue is |
I would separate these checkboxes into categories, so you get somethings like this. WDYT?
|
I think push should align with the GitHub push event, i.e. Branch/tag CRUD The other stuff would be a great feature request, but missing the D on this is a bug |
I also think that too many options is bad for users. GitHub has it about right: You just need to fix this bug on how you process Push events... which should include pushes like The PUSH events currently are missing, clear bug. The other events that GitHub offers are RFEs and should probably be in a separate issue |
If a hook is missing that never was there in the first place it's still a FE, not a bug ;) |
Well you already have a "Push" hook that promises "Git push to a repository" and I am showing that it does not deliver all git pushes to a repository... only the Cr & U of CrUD... so sounds very like a bug.... I am not asking for a new hook in this issue... only for the existing hook to publish all the "git push to a repository" that it currently advertises Now you could fix this in one of two ways:
Either of those are perfectly valid fixes to the bug... obviously I would be a Sad Panda if you chose the "change the documentation" route. BTW when you fix this then https://github.com/jenkinsci/gitea-plugin will be a really sweet integration for gitea with Jenkins... right now, without the Push event publishing the D of CrUD you have to force scanning far far too often in order to clear out deleted branches |
Someone's working on that? |
@daviian I don't think so, go ahead |
IMO issue can be closed now as #2530 has been merged |
[x]
): N/ADescription
When I configure a webhook that receives all events, push events that remove a branch or branch removal of the branch through the UI do not trigger a webhook event:
Creation of a new branch results in events like:
X-Gitea-Event: create
and
X-Gitea-Event: push
I would expect removal of the branch to trigger at least a webhook that looked something like:
X-Gitea-Event: push
It is a somewhat separate concern the use of a magic value to indicate no ref, better would be to include the created and deleted booleans that GitHub does, but for my part the only concern I have is the lack of a
push
event to catch branch removal.The text was updated successfully, but these errors were encountered: