Opbeat is joining forces with Elastic – Learn more about Elastic APM

Why does Opbeat need private repo access on GitHub?

We need private repo access on GitHub to show the commits that make up a Release, as well as the information in the annotated stacktraces (who last edited a given line, which release was that line last included in etc.).

We are aware of the privilege we get with the level of access to your private repos, and we only use it to get information we need to give you the best experience with Opbeat.

Due to a limitation in GitHub’s API, we ask for read-write access to all of your repos, even though we only need read access to your connected repo. When GitHub changes their API, we will modify the permission request. (Alternatively, you can use our custom Git integration)