Sentry: Find out if we can use Suspect Commits #1921

Open
opened 2022-05-21 14:05:30 +00:00 by dpschen · 5 comments
Member

In order to get a better understanding which commits broke something we might awnt to use the "suspect commits" feature of sentry.

In order to get a better understanding which commits broke something we might awnt to use the "suspect commits" feature of sentry.
dpschen added the
area/internal-code
label 2022-05-21 14:05:30 +00:00
Owner

Does this work with Gitea?

Does this work with Gitea?
dpschen changed title from Sentry: Enable Suspect Commits to Sentry: Find out if we can use Suspect Commits 2022-05-22 15:12:43 +00:00
Author
Member

Not sure

Not sure
Author
Member
Related: https://kolaente.dev/vikunja/frontend/pulls/1991
Author
Member
Related: https://kolaente.dev/vikunja/frontend/issues/1980
Author
Member

I found this part of the documentation: https://docs.sentry.io/product/releases/suspect-commits/#using-the-cli
Somehow I always missed that until now.

I found this part of the documentation: https://docs.sentry.io/product/releases/suspect-commits/#using-the-cli Somehow I always missed that until now.
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: vikunja/vikunja#1921
No description provided.