AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Sourcetree file history2/1/2024 Awesome Graphs for Bitbucket add-on as a tool with wide search opportunities and various analytical features.Sourcetree as a free application that is suitable for searching among a small number of repositories.We’ve described different ways to work with commits effectively: Learn more about the available REST API resources. Use this request to get a list of commits from the specified repository. The solution allows you to retrieve data faster while decreasing the load on the instance compared to Bitbucket REST API. Īlternatively, you can use the Awesome Graphs REST API that provides global, user, project, and repository data. Merges parameter controls how to handle merge commits – exclude merge commits, include both merge commits and non-merge commits, or only return merge commits. For instance, since and until options help to get the commits made after or before a certain commit, or between two commits defined by their IDs. The request can be extended by specific parameters to receive a more accurate result. Search for commits in Bitbucket via REST APIīitbucket REST API provides a possibility to get the list of all commits in the repository using this request. You can access the in-app documentation (accessible to Awesome Graphs’ users) by choosing Export → REST API on the People page or go to our documentation website. Īnother way to export commit data to CSV is to use the Awesome Graphs REST API, which allows you to automate the processes and retrieve this data easier using the dedicated resources. There you’ll notice the Export menu at the top-right corner, where you can choose CSV. To export raw commit data to CSV directly from Bitbucket, you need to go to the People page. As a result, you’ll get a list of commits with their details: In general, its use-case is to find the most active contributors of the project or repository, but you can configure the Period of time and choose Authors of the commits you’re searching for.Īs a result, it shows the list of all commits for the selected time span in the Activity section below as well as their distribution in time.Īwesome Graphs for Bitbucket also gives you the capability to export commit data to CSV in different ways. It shows all commits for the last year or a shorter time span in the Activity section below the charts.Īnd if you need to find commits made long ago, the Top Committers Report can be a good solution. This helps us alter the commit history and remove the history we deleted earlier.In order to find the commits made to a certain repository regardless of their author, use the Activity graph. Now, we'll modify this by deleting the text “ pick 535f7ea blob file removed “. message (or the oneline, if no original merge commit was create a merge commit using the original merge commit's # l, label = label current HEAD with a name # b, break = stop here (continue rebase later with 'git rebase -continue') # x, exec = run command (the rest of the line) using shell # f, fixup = like "squash", but discard this commit's log message # s, squash = use commit, but meld into previous commit # e, edit = use commit, but stop for amending # r, reword = use commit, but edit the commit message This opens our nano editor showing: pick 535f7ea blob file removed With this command, we enter into an interactive rebase: $ git rebase -i 5bac30b So we'll use the SHA1 key from the history of the entry preceding the one we want to remove. Our aim is to remove the blob file from our commit history. * 535f7ea (HEAD -> master) blob file removed We need the SHA1 key from the git log to use this approach: $ git log -graph -full-history -all -pretty=format:"%h%x09%d%x20%s"
0 Comments
Read More
Leave a Reply. |