-
Notifications
You must be signed in to change notification settings - Fork 13
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
feat: remodling EventDelete to resemble EventTag #348
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #348 +/- ##
==========================================
- Coverage 96.58% 96.45% -0.13%
==========================================
Files 70 69 -1
Lines 7494 7476 -18
==========================================
- Hits 7238 7211 -27
- Misses 185 193 +8
- Partials 71 72 +1
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry, i missed these in the first go
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think it's looking good; just one more request to provide more detail. see within.
Every time a tag or branch are deleted in GitHub, both a delete and push webhook are sent out. Previously I used the delete webhook and had EventDelete modeled off of EventPush, EventPR, EventDeploy, and EventComment in how they are their own event not related to the others. However, the push webhook that is sent out with the delete webhook contains more relevant information that can solve some of the issues that were found with only having the delete webhook data (such as missing a commit and not being able to properly set the BUILD_TAG environment variable).
Therefore, EventDelete has been lumped in with push events, in the same way that EventTag has been.