Tracing and Analyzing Renamed/Copied Files in Bitbucket Server with GitSense

In our previous blog post, we quickly went over how GitSense, makes diffing in Bitbucket Server better.  In this blog post, we'll continue our theme of making Bitbucket Server better, by quickly highlighting how it can be used to trace and analyze renamed and copied files.

If you would like to install GitSense for Bitbucket Server, you can download both the GitSense Server and Bitbucket addon-on for free.  And if would like to play around with the add-on, you can do so at http://bitbucket-server-demo.gitsense.com.  If you are learning about GitSense for the first time, we recommend you read our previous blog posts, to learn more.

Making GitSense of Renamed and Copied Files

In the screenshot below, you can see an example, of what a renamed file looks like in Bitbucket Server.

If you are familiar with Bitbucket Cloud, GitHub, or GitLab, you may also notice, there is no previous file information ... well, other than in the commit comment.  It is kind of perculiar, that this information was left out.  Luckily, GitSense can help with that.  With GitSense, it can tell you what the previous file was, and much more.

So as you can see, with GitSense, it provides more than just the previous filename, it provides a smarter way to look at your codes history.  If you want to try what was shown in video above, you can use the following link, to view the commit in question.

http://bitbucket-server-demo.gitsense.com/plugins/servlet/gitsense/ACME/chakracore#b=bitbucket-server:ACME/chakracore:master&q=commit:afb1b86acc

Well this brings us to end of this blog post and usual, we hope it was informative.  With GitSense, we are constantly thinking of different ways to increase developer productivity, so stay tuned for future blog posts.

Blog Posts

© 2016 SDE Solutions, Inc. All rights reserved.