I believe I have everything set up properly with my organization -
And my personal account as well, which has my personal github identity associated with it.
And yet I still see this warning that I haven’t associated any commits yet:
Am I missing a step?
I might be missing one step:
Under your organization, go to “Repositories” and add the repo(s) you want to track commits for.
Per my initial post (#2), I’ve already done that, no?
As for the sentry organization configuration, I’ve got the two repos specified there as well.
@zeeg it seems like you’re the only person from Sentry who monitors this forum. Could you help me? I’d really like to be able to maximize the product, but it seems I’m stuck at at impasse.
To associate commits you have to use the release API - you need to indicate which commits are part of which release.
Thanks for responding.
FWIW the docs are a bit misleading:
“There are two ways to create a release and associate commits: using a repository integration (recommended), or by manually supplying Sentry with your own commit metadata.”
And there’s two major headings for each supposed way of doing things. Might make sense to change the language there to be more specific.
Sent your feedback over to the team - and I agree. You cant actually couple commits to releases by just connecting to the repository. It just makes it easier to select a delta of commits since we can then look it up from the upstream provider.
I’ve run into the same issue. The documentation is still worded rather confusing as it still sounds like an “either / or” option.
We just ran into the same issue as well. The documentation is still unclear about the fact that you have to associate commits manually despite connecting the repo via integrations.
As a side note: I don’t remember having to manually associate commits on a sentry project I worked on a few years go, it auto-detected the commits between the commits of each release, does it not do that anymore, if so what changed? Why do we have to manually associate commits now?
