Why am I receiving the email "Unable to Fetch Commits"?

If you received an email notifying you that we were unable to fetch the commit log for your release, try out some of the solutions below:

Make sure that the commits exist in the repository. This error can happen when you forget to push to GitHub or you squash and merge commits.

GitHub

GitHub returned a 404 Not Found error. If this repository exists, ensure that your installation has permission to access this repository (https://github.com/settings/installations).

If you have already confirmed the correct permissions from the message above:

• Your GitHub identities in Sentry may not be synced up with the user who is creating the release in Sentry.
• If you have already connected your identity and are still receiving this message, you may need to disconnect or reconnect your identity.
• All Sentry users will need to do this if they are creating releases.
• Try the troubleshooting steps in this Help Center article.

Unauthorized: either your access token was invalid or you do not have access

• Confirm that the Auth Token being used to create the release in Sentry has the correct scopes and is also associated with the GitHub identity of the user who is creating releases in Sentry.
• You may also need to disconnect/reconnect your GitHub identity as mentioned above.

GitLab

If you have received the “Unable to Fetch Commits” email and/or cannot access the GitLab integration configuration page, the immediate solution is to uninstall and reinstall the integration. Due to some breaking changes to expiration tokens introduced in GitLab 15.0, your GitLab integration in Sentry may have become corrupted.

Please note that all integration data will be lost with reinstallation. This includes links to Sentry issues, repositories, and any mappings that have been set up.

We plan to make changes to prevent any further issues from occurring, and apologize for the inconvenience. You can read more about the issue here.

Bitbucket

Error Communicating with Bitbucket (HTTP 500): Something went wrong

• Unfortunately, this message usually indicates that there’s something wrong on Bitbucket’s end. We suggest to try and associate the commits with the release again.