Feature #35432

Git: View annotate prior to the change

Added by Go MAEDA over 1 year ago. Updated 3 months ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:SCM
Target version:5.1.0
Resolution:

Description

The "Blame" view of GitHub and Gitlab has a feature called "View blame prior to this change". With the feature, you can easily jump to an older change of the line.

I think it would be useful if Redmine also has the feature. Currently, it requires some manual steps to see older changes in the "Annotate" view of Redmine.

gitlab-view-blame-prior-to-this-change.png (124 KB) Go MAEDA, 2021-06-22 10:00

35432.patch Magnifier (6.09 KB) Takenori TAKAKI, 2021-07-08 09:59

disp_link_to_prior.png (231 KB) Takenori TAKAKI, 2021-07-08 10:00

0001-Git-View-annotate-prior-to-the-change.patch Magnifier (288 KB) Go MAEDA, 2022-09-03 09:35

History

#1 Updated by Takenori TAKAKI over 1 year ago

I made a patch to display the link to prior revision.
The patch adds a link to "Annotate" view as follows

#2 Updated by Go MAEDA over 1 year ago

  • Target version set to Candidate for next major release

#3 Updated by Mischa The Evil over 1 year ago

  • Subject changed from View annotate prior to the change to Git: View annotate prior to the change

+1 This is a real handy feature when browsing (Git) repositories a lot. Given the usability of this change I wonder if this is something that could be implemented (easily) for other SCMs (Hg, SVN, ...) too?!

#4 Updated by Go MAEDA about 1 year ago

Mischa The Evil wrote:

Given the usability of this change I wonder if this is something that could be implemented (easily) for other SCMs (Hg, SVN, ...) too?!

This feature is easy to implement in the Git adapter because `git blame -p` outputs the previous commit for the line, as shown in the "previous" like of the following sample.

However, `blame` / `annotate` subcommand of other SCMs such as subversion doesn't give the information of the previous change, so we have to find another way to get the previous change.

Since there are so many Git users these days, I think it is a good idea only for Git as a first step.

c91a4391d34b9bd97270d20f04aeb40ee64166a1 1 1 1
author Jean-Philippe Lang
author-mail <jp_lang@yahoo.fr>
author-time 1476985764
author-tz +0000
committer Jean-Philippe Lang
committer-mail <jp_lang@yahoo.fr>
committer-time 1476985764
committer-tz +0000
summary Set https back.
previous 15460450bbe72a756015e16689bcafe5a6b1164b Gemfile
filename Gemfile
        source 'https://rubygems.org'
9315039e0a95b0234b7736f359fc039550f45e08 2 2 1
author Jean-Philippe Lang
author-mail <jp_lang@yahoo.fr>
author-time 1329661846
author-tz +0000
committer Jean-Philippe Lang
committer-mail <jp_lang@yahoo.fr>
committer-time 1329661846
committer-tz +0000
summary Use Bundler for gem management (#5638).
filename Gemfile

#5 Updated by Go MAEDA 5 months ago

  • Target version changed from Candidate for next major release to 5.1.0

Setting the target version to 5.1.0.

#6 Updated by Go MAEDA 3 months ago

Updated the patch for the current trunk r21799.

Also available in: Atom PDF