5
For Suspect Commits, ignore commits from .git-blame-ignore-revs
Source: getsentry/sentry#87383 · opened by @armenzg
Environment
SaaS (
Steps to Reproduce
1. Write some code that will trigger a Sentry error
2. Add your commit to .git-blame-ignore-revs
3. Push the code live and trigger the bug
Expected Result
Sentry does not suggest that commit in the Suspect Commit
Actual Result
Sentry shows that commit as the Suspect Commit
Product Area
Issues
Link
_No response_
DSN
_No response_
Version
_No response_
SaaS (
Steps to Reproduce
1. Write some code that will trigger a Sentry error
2. Add your commit to .git-blame-ignore-revs
3. Push the code live and trigger the bug
Expected Result
Sentry does not suggest that commit in the Suspect Commit
Actual Result
Sentry shows that commit as the Suspect Commit
Product Area
Issues
Link
_No response_
DSN
_No response_
Version
_No response_
No pledges yet. Be the first to back this.
Comments
Similar requests
[suspect commits] Add a way to configure how long a commit will be considered as a suspect commit // Lower the time threshold
0 votes · 0 comments
Add line-level, blame-based suspect commits for Azure DevOps
1 vote · 0 comments
Option to disable Suspected Commits
1 vote · 0 comments
Use user mappings for deploy "my commits" notifications
0 votes · 0 comments
Create Issues from OpenTelemetry exceptions (OTLP exception log records and span events)
0 votes · 0 comments
No comments yet.