diff --git a/src/docs/product/issues/suspect-commits/index.mdx b/src/docs/product/issues/suspect-commits/index.mdx index 530893463e0ff..72826404f8383 100644 --- a/src/docs/product/issues/suspect-commits/index.mdx +++ b/src/docs/product/issues/suspect-commits/index.mdx @@ -16,9 +16,20 @@ When you've enabled suspect commits, we can tie together issues with the commits - Files touched by those commits - Authors of those files -Suspect commits and suggested assignees are then displayed on the **Issue Details** page in [sentry.io](https://sentry.io): - -![The suspect commits and suggested assignees for an issue](suspect-commits-highlighted.png) +Suspect commits and suggested assignees are then displayed on the **Issue Details** page in [sentry.io](https://sentry.io), as shown below. + +
+ +
## Enable Suspect Commits @@ -63,6 +74,23 @@ Sentry will automatically try to set up code mappings on Python and JavaScript p The first frame in the stack trace is considered suspect when looking at them top-down. If the first frame is not in-app, the next frame is considered suspect. +### UI Walkthrough + +Follow along with the animated gif below to see how to integrate your GitHub account and repository. + +
+ +
+ ## Suspect Commits Without Integrations You can send us your commit data [manually](/product/releases/associate-commits/) if: