GitHub Integration Problem
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 22h 21m
- Merged PRs (30d)
- 586
Description
### Environment
SaaS (https://sentry.io/)
### Steps to Reproduce
1. initiate integration with GitHub from Sentry UI
2. choose a single repo in the GitHub UI when asked
3. submit the configuration for approval
4. have someone with appropriate rights within the GitHub organization approve the Sentry.io app installation
5. notice it's not showing up in Sentry's UI
6. ask the other person to upgrade the rights to include everything in the organization
7. still find that the integration is not working
8. remove Sentry from GitHub
9. have the other person initiate the integration and choose the whole organization
10. find that that time it worked
### Expected Result
I would have expected that
1. if it is necessary to grant rights to the whole organization, that would have been displayed prominently
2. a failure could have been displayed in the Sentry UI with some indication of what went wrong
3. changing the rights to the appropriate rights might have made it start working
### Actual Result
It was necessary to start from scratch, and basically infer that Sentry needed full-org rights. (As far as I recall that was not explicitly stated anywhere, but I might have missed it.)
### Product Area
Settings - Integrations
### Link
_No response_
### DSN
_No response_
### Version
_No response_
Contributor guide
Research direction
Start in Sentry's Settings - Integrations flow and reproduce the GitHub installation steps described in the issue, first selecting a single repository and then the whole organization. Check how approval, permission changes, and failed installations are surfaced in the Sentry UI. Done means the required organization rights are clearly explained and an actionable failure state is shown without requiring the integration to be started over.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- authorization, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100