Show Suspect Commit

[sdzhong]

Suspect Commit are not appearing on the flagship error (tda-generated, locally generated)

However, they were consistently appearing in tda-generated events and from a local run (event).

What is preventing Suspect Commit from consistently/reliably appearing?

[sdzhong]

May be related to getsentry/sentry#55013, since the Suspect Commit commit is > 1 year old.

Next step: update the flagship error so git blame / Suspect Commit chooses a recent commit (less than 1 year old) instead

[sdzhong]

This may be resolved as a side-effect of #68

[sdzhong]

Suspect Commit appeared when running locally, e.g. when testing https://github.com/sentry-demos/android/tree/feat/profiling-issues, I see this event with Suspect Commit:

I don't see it in subsequent events, though (whether those events are generated locally or via pytest).

[sdzhong]

Suspect Commit appears in 2.6.1

Example event URL

^Potential bug showing me as You committed and also sdzhong committed, both referring to me.

[sdzhong]

I’ve added the suggested email 89550162+sdzhong@users.noreply.github.com to https://demo.sentry.io/settings/account/emails/.
Now the event shows You committed for all.