[GitHub Integration] Commits not associated with release
- 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. Install GitHub Integration.
2. Create new release.
### Expected Result
A new release is logged along with the associated commits and changed files.
### Actual Result
New release is logged, but commits and changed files are empty.
### Product Area
Releases
### Link
_No response_
### DSN
https://888e5a0778212e1d0314c37d4b9aae5d@o4504521589325824.ingest.us.sentry.io/4504521592406016
### Version
_No response_
Contributor guide
Research direction
Start by reproducing the issue in the SaaS environment with the GitHub Integration and a newly created release. Trace the Releases integration flow to find why associated commits and changed files are empty. Done means a new release includes its associated commits and changed files, matching the expected result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, python
- Domain
- backend, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100