installation_repositories webhook: no "removed" event when switching from "All repositories" to "Only select repositories
#191199
Replies: 1 comment
-
|
Good catch — this is a known gap in how GitHub handles the installation_repositories webhook during that specific transition. Short answer: Yes, this is the current behavior, and it's arguably a bug or at minimum an undocumented edge case. You won't receive a removed event for repositories that lose Why it happens: When an installation is set to "All repositories," GitHub doesn't internally maintain an explicit list of individual repos — it's stored as a flag (essentially The reverse transition works correctly because GitHub does have an explicit list (the selected repos) and can diff it against the full set. Recommended workarounds:
If you want this fixed properly, consider filing this as a bug report through https://support.github.com/contact or in the |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Webhooks
Body
When a user changes their GitHub App installation from "All repositories" to "Only select repositories," an
installation_repositoriesevent with actionaddedis sent containing the selected repos. However, noremovedevent is sent for the repositories that lost access.The reverse (switching from "Select" to "All") correctly sends only the newly gained repos as
added, accounting for already-selected repos.Is this the expected behavior? If so, what's the recommended approach for detecting which repositories lost access during this transition?
Beta Was this translation helpful? Give feedback.
All reactions