I have successfully set up the github integration for my project. I create releases and deploys using the sentry-cli and I can see the results of this in the github information associated with new issues and releases in the Sentry web UI. When creating a release, I use the “sentry-cli releases set-commits --auto” command, then I follow that up with an eventual “sentry-cli releases finalize”.
However, I am curious to know when Sentry decides to mark Sentry issues as “resolved” due to any “Fixes SENTRY-123” entries in the release’s commits. I see several likely candidates:
- When the “set-commits” command provides the commits for the release
- When a deploy is created for the release (in my case this would be after the “set-commits” step.
- When the release is finalized with the “sentry-cli releases finalize” command
I’m hoping it’s triggered by the finalize step, as that seems like a clean demarcation with the least chance of prematurely resolving issues just to have them reopen if the event occurs again (which is almost guaranteed if one has pre-production environments that get the code first while the issue is still affecting production). This would also allow one to create the release prior to deploying to staging environments and add commits to the release if more issues are discovered and fixed during pre-production testing.
Does anyone know for certain?
Additionally, does anyone know what purpose the “finalize” command serves? It’s not really clear from the documentation.