-
Notifications
You must be signed in to change notification settings - Fork 736
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
Do not populate repo list in case of installation:deleted event #1690
Conversation
@Haarolean Looking at this - Maybe the right solution here is to change the event to have Either way we'll need an additional test for the installation that covers |
@bitwiseman I'll try to look into this later this week. Both the suggested approach and a seprate test. |
@bitwiseman I think I've done what we've discussed above. I've used a real recent webhook payload, but replaced a repo within it with the one we already have captured data for, I don't think that's critical to capture a snapshot here for just that. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1690 +/- ##
============================================
+ Coverage 80.66% 80.73% +0.06%
Complexity 2342 2342
============================================
Files 220 220
Lines 7082 7096 +14
Branches 379 379
============================================
+ Hits 5713 5729 +16
Misses 1132 1132
+ Partials 237 235 -2 ☔ View full report in Codecov by Sentry. |
@bitwiseman thank you! |
Description
Closes #1689
That's a proposition of a solution I came up with.
Unfortunately I haven't been able to run the whole test suite due to the same repeating exception occurring and I didn't have time to look into that.
Before submitting a PR:
@link
JavaDoc entries to the relevant documentation on https://docs.github.com/en/rest .mvn -D enable-ci clean install site
locally. If this command doesn't succeed, your change will not pass CI.main
. You will create your PR from that branch.When creating a PR: