Issue
Often times whenever I associate commits to my release, I always get the last 20 commits pulled instead of just the ones that are relevant to this specific release.
Applies To
- Users of sentry-cli set-commits
- Users of any of the bundler plugins with the setCommits option
- Any other Sentry integration that manages releases
Resolution
When the set-commits command is run, Sentry will first check the previous release by timestamp for any associated commits. If the previous release does not have any commits associated, then the default last 20 will be grabbed. To ensure you have the correct commits associated, the set-commits command should be run every time for all releases.