As part of our CI build in Azure DevOps we now have Releases getting auto created and debug files being uploaded. That CI runs everytime I push to the remote repo. Should I only be creating Releases as part of a build that will go to the App Stores? maybe just one that will be used by the Test team or is it OK to just create Releases on every CI run?
#When to Auto Create a Release and when to not bother
dry hamlet
odd smelt
I would argue that creating too many releases that don't correspond to actual deployments might make it harder to track meaningful changes and could potentially clutter your Sentry dashboard.
dry hamlet
That's what I am thinking I might add a manual step to to the CI that confirms a Release or not