-
-
Notifications
You must be signed in to change notification settings - Fork 112
Sentry workflow
Marc Durdin edited this page Nov 23, 2020
·
1 revision
Sentry issues will disappear over time. So it is pretty essential for our ongoing maintenance and record of changes that we put all relevant content into GitHub issues.
When we want to address an issue raised on sentry.keyman.com, we should:
-
Click the
Link GitHub Issue
link on the right side of the Sentry issue page. -
Make sure that enough details are present in the issue we create that we don't need to go back to Sentry (callstack, environment, versions, etc).
(Don't just reference the Sentry issue as a link from a GitHub Pull Request/Issue; follow the steps above and paste in additional content as required.)
-
When the PR lands, go back and mark the Sentry issue as 'resolved in next release'.