I have noticed some discrepancies between code owners updates through the API and when using the CODEOWNERS file from Github. In Github, you can pull users using Github names and then map the Github name to a Sentry user on a separate page. However, when using your API, we are required to send only Sentry emails; Github names are not allowed.
This can be an issue because there might not be internal mapping between GitHub names and employee emails.
Even if mapping is created, there is no guarantee that the user already has an account in Sentry; otherwise, the request will fail.
Solution Brainstorm
Allow sending GitHub names using the API once the Github integration is setup successfully.
Problem Statement
I have noticed some discrepancies between code owners updates through the API and when using the CODEOWNERS file from Github. In Github, you can pull users using Github names and then map the Github name to a Sentry user on a separate page. However, when using your API, we are required to send only Sentry emails; Github names are not allowed.
This can be an issue because there might not be internal mapping between GitHub names and employee emails.
Even if mapping is created, there is no guarantee that the user already has an account in Sentry; otherwise, the request will fail.
Solution Brainstorm
Allow sending GitHub names using the API once the Github integration is setup successfully.
Product Area
APIs
┆Issue is synchronized with this Jira Improvement by Unito