Handle "named branch" for mercurial
|Assignee:||Toshi MARUYAMA||% Done:|
Mercurial has a concept of branches inside the same repository (as opposed to "use another repository as branch"). Currently, redmine only 'sees' the main branch and not the other ones.Handling the named branches would mean:
- see commits from those branches in the repository tab (/projects/xx/repository/, /projects/xx/repository/revisions, individual file revision logs, ...)
- use commits on those branches when matching for 'fixes' 'refs' and other actions
scm: mercurial: support named branches at adapter (#7246).
Contributed by Yuya Nishihara.
scm: mercurial: add test of latest changesets support named branch in unit model test (#7246).
Git and Mercurial support branch.
Git in repository root shows master branch.
Git master branch does not have all revisions.
Mercurial default branch is default branch.
Mercurial shows tip in repository root.
Mercurial does not treat directory. "hg log DIR" costs high.
Getting correct limited changesets in sub directory and branch is very heavy.
So, if there is no recent revision in sub directory and branch,
no changeset shows.
#2 Updated by Toshi MARUYAMA over 6 years ago
- File hg-root.png added
- File hg-1.1-stable-rev.png added
- File hg-1.1-stable-url-path.png added
- File hg-1.1-stable-file.png added
- Status changed from New to Closed
- Target version set to 1.2.0
- % Done changed from 70 to 0
- Resolution set to Fixed
We finished implementing the feature of Mercurial named branches browsing based on git branches implementation in #1406.
These are images of Redmine hgsubversion mirror.
There is a discussion about the top page of a repository.
Please see #7984.
use commits on those branches when matching for 'fixes' 'refs' and other actions
I can not understand your request.
Please create new issue with descriptions in detail.