Overview 

In this article, we will walk you through all the perks of integrating GitHub source control with your Rollbar projects. Once you have source control integration set up and a Git repository is connected to your Rollbar projects, you will have more visibility on:

  • where the error was most recently activated,
  • the context of the code line where the bug occurred, and 
  • who the last person was to work on the affected code section, thus being able to assign it to the right person to work on it and resolve it faster. 

Additionally, you won’t even have to leave your Rollbar project. Sounds tempting, right? Let's get to it!


Don’t have time to read? Watch our short video and learn the benefits in just 2 minutes, and save our article for later!

Gain more visibility all in one place

When a Rollbar project is connected to a Git repo, stack traces will include links to each file in the code version where the error was most recently activated. 

Another advantage is that the list of commits included in each deploy will include URLs so you can view the difference for each commit as well as the entire deployed code version, thus spotting where the error occurred and fixing it with ease.

You will also have the chance to view un-deployed commits. Any commit that has been merged to your master branch but not yet deployed will be highlighted at the top of the Deploys screen. This will provide more visibility for developers who have missed the commits while deploying to act quickly upon them.

The commits in each deploy and the un-deployed commits are visible under the Deploys tab after you select the project and the environment you want to check.

Get more context around your errors

Once you have source control integration set-up with GitHub, we can pull the code context directly from GitHub into the Item details page in the Rollbar UI. You will be able to see the offending piece of code, and additionally, you will have visibility of what happens right before and after that line of code

With this integration, you will have context around your errors in one convenient location. There is no need to switch between GitHub and Rollbar trying to match up the lines of codes!

Git Blame, but no blame

Let’s say you got a new notification coming in, about an error that has just occurred. You might want to get more information on who was the last one to work on that piece of code. 

With your project connected to the Git repo, we can provide this information conveniently in the Rollbar UI with the help. You will see the GitHub User Avatar of the last developer to edit the line of code that triggered the error. The User Avatar will provide additional information on the pull request and the date and time of the commit.

With Git Blame, you will have the information on when the code was written and by whom, thus you can quickly assign the developer who was the last to work on it and probably has knowledge around those specific lines of code which can help to fix the error quickly.

Set-up source control for your projects

Take your Rollbar experience to the next level and integrate the GitHub source control with each of your projects! Check out our GitHub Docs for easy set-up. 

Want to learn more? Read our article on the benefits of keeping an eye on your deploys with the help of Deploy tracking.

Did this answer your question?