New GitHub integration

Robert Robert Beekman on

We’ve improved our GitHub integration!

Since the very beginning of our GitHub integration we were asked why we needed access to customer’s code. This had everything to do with the available OAuth scopes GitHub implemented at the time, it was an all-or-nothing-deal.

GitHub announced a new way of integrating with GitHub, named “apps”. With this new integration the user has fine-grained control over what AppSignal can access on GitHub.

Our current feature set mainly revolves around creating issues straight from AppSignal and we’d like to start tracking deploys from GitHub. Therefore we will only request access to these two segments of your selected GitHub repositories. We won’t have access to your source code or any other part of GitHub.

We feel this is an important step to make our integration more secure, so we’ve decided to disable the old (GitHub OAuth) integration completely. This requires all users to go through the new one-time app-based OAuth flow that will look like this:

GitHub OAuth screenshot

We also require you to re-create the integration and link the repositories to AppSignal Apps. We made a new GitHub integration screen that should make this upgrade a breeze in comparison to the old integration. This screen can be found in the “Profile & Settings” section for every organization you’re an owner of, on the “Integrations” page.

GitHub integration page

With this upgrade we believe we have a solid and secure base to roll out more GitHub related features in the future.

If you have any questions don’t hesitate to contact our awesome support team on

10 latest articles

Go back
Ruby magic icon

Subscribe to

Ruby Magic

Magicians never share their secrets. But we do. Sign up for our Ruby Magic email series and receive deep insights about garbage collection, memory allocation, concurrency and much more.

We'd like to set cookies, read why.