Defect #3515

Sensible Git repository branches

Added by Carl-Johan Sveningsson over 13 years ago. Updated over 13 years ago.

Status:ClosedStart date:2009-06-19
Priority:NormalDue date:
Assignee:-% Done:


Target version:-
Resolution:Duplicate Affected version:


It seems Redmine currently is only able to display the branch named "master" (which is actually an arbitrary and non-sanctioned default?) which may be a sensible limitation to make with other SCM software, but seems unnecessary with Git.

Because branches in Git are not much more than labels on the heads of directed linked lists of commits, and because Redmine (nor the official Gitweb actually) has any real capability to manage branches, it could make sense to just show the revision log as a chronological list of all commits. Gitweb is also discriminating commits on basis of belonging to a certain branch, but if a branch is a subset of the displayed branch, this is also showed as a label in the list - I'll attach an example when displaying the =21fixes= branch.

Currently we are using many other branches than master in our repositories, and while it would be great to get the links to redmine issues, the Git repository integration needs a bit more basic functionality to be usable for us.

I'm not a returning redmine contributor, so I would be happy to receive email updates or possibly discussion in the IRC channel

Best regards
CJ Sveningsson, Estonia

git-gitweb.png (171 KB) Carl-Johan Sveningsson, 2009-06-19 11:46

Related issues

Related to Redmine - Feature #1406: Browse through Git branches Closed 2008-06-09


#2 Updated by Carl-Johan Sveningsson over 13 years ago

I found this discussion related to the topic:

#3 Updated by Adam Soltys over 13 years ago

An issue for this already exists: #1406
I'm just starting to work on a patch to address the problem. You can follow my progress at

#4 Updated by Carl-Johan Sveningsson over 13 years ago

  • Status changed from New to Resolved

#5 Updated by Eric Davis over 13 years ago

  • Status changed from Resolved to Closed
  • Resolution set to Duplicate

Completed in issue #1406

Also available in: Atom PDF