Git blame commit number12/5/2023 ![]() ![]() Code Context with Git blame in a Rollbar Item - An Example While ‘git blame’ might suggest you can blame someone and go about your work, we strongly recommend using it for getting more context on the code and assigning someone to the error when it makes sense. Assign the error to the last author if needed.Get context on the history of the code and why, how the code was added. ![]() Correlate when the code was written to the date and time of the item occurrence to help triage the error.See who the last author was to edit the line of code that caused the error.No more switching back and forth between Rollbar and GitHub! If you hover over the Avatar, you can directly visit the pull request and the commit for that code. You can directly see the GitHub User Avatar of the last person to edit the offending line of code in Rollbar. You don’t have to go to GitHub anymore to get this information. Now, you may want to get more context on who should be assigned to the error or why some changes to the code were made. As you click on the Traceback in the Item details page, you can see the exact line of the code that caused the error in each frame of the stack trace directly within the Rollbar UI. Let’s say a new error pops up in Rollbar that you would like to investigate. Now, we’re excited to support git blame to help you identify the last person to write or edit the line of code that caused the error, directly within the Rollbar UI. Last year, we launched Code Context to show additional lines of code within each frame of the stack trace, reducing the back and forth between GitHub and Rollbar. This is why we’re making our integration with GitHub even stronger to provide more context around errors and reduce the mean time it takes to resolve them MTTR. At Rollbar, we care about reducing the time it takes developers to find and fix errors. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |