As part of the ongoing development of features like Seer’s issue fix and code review, we’re updating the Sentry GitHub App to request write access to repository contents.
This permission is only used when you run features that propose code fixes via pull requests.
- Why is Sentry asking for write permissions?
- In order for Sentry to automatically create Pull Requests in your GitHub repositories, we need
write:contentpermission to create new branches for the Pull Request.
- In order for Sentry to automatically create Pull Requests in your GitHub repositories, we need
- Will Sentry make changes to my codebase directly?
- Sentry has no intention on making changes to your codebase directly without a Pull Request.
- What can I do to protect my codebase if I want to be extra careful?
- You can utilize Branch Protection Rules and Rulesets to prevent any unwanted changes.
- Will Sentry store my code?
- No, we pull the required code from GitHub directly when needed and we never store them on the Sentry Infrastructure after the job is completed.
- For more information about how Sentry handles your data please see our Trust Center.
- Is it common for developer tools that integrate with GitHub to ask for these permissions?
- Yes, almost all of the developer tools that can create Pull Request for you requires this permission.
- What if I don’t want to accept the new permission?
- You are not required to accept the permission. The request from GitHub will remain in place in an unaccepted state as long as the integration is installed.
- Can I uninstall the Seer GitHub App after I accepted the new permission?
- Not yet, we are planning to slowly deprecate the Seer GitHub App after the permission changes and we will keep you updated when it’s ready to remove the Seer GitHub App.
- I have not accepted the new permission, how will Sentry work?
- All the existing features will continue to work as they use to, however you may not be able to utilize new features that’s available in Sentry.
- I have both GitHub and GitHub Enterprise integrations installed, do I need to take additional action?
- If you want to ensure parity across repositories in both integrations - you’ll need to add the
write:contentpermission to the GitHub App in your GHE installation.
- If you want to ensure parity across repositories in both integrations - you’ll need to add the
You can read more about GitHub permissions in our documentation: https://docs.sentry.io/organization/integrations/source-code-mgmt/github/#github-permissions