You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to use Sentry Associate Commits feature.
This has a few advantages, but the main one I believe is to have GihHub links to redirect to specific commit of the error, rather than always to develop.
E.g. after doing such command locally, I have it working for v6.1.0-4-g9b495951f:
And the GitHub link goes to certain commit (wrong commit in this case,
WITHIN status-go repository
WHEN a tag is pushed
AND tag matches v* (e.g. v6.2.0) pattern
WITH provided SENTRY_AUTH_TOKEN (setup one here)
RUN this command:
Description
We want to use Sentry Associate Commits feature.
This has a few advantages, but the main one I believe is to have GihHub links to redirect to specific commit of the error, rather than always to
develop
.E.g. after doing such command locally, I have it working for v6.1.0-4-g9b495951f:
And the GitHub link goes to certain commit (wrong commit in this case,
Pre-requesites
Requirements
WITHIN
status-go
repositoryWHEN a tag is pushed
AND tag matches
v*
(e.g.v6.2.0
) patternWITH provided
SENTRY_AUTH_TOKEN
(setup one here)RUN this command:
The text was updated successfully, but these errors were encountered: