Feature #5279

Branch level associations between projects and repositories.

Added by Jeffrey Jones over 12 years ago.

Status:NewStart date:2010-04-09
Priority:LowDue date:
Assignee:-% Done:


Target version:-


I am in a situation where I have two versions of one piece of software.

One is a version that is used in production and another is a version that is used for presentation purposes.

Currently I have one parent project for the software with two sub-projects for issues etc.

- Production Version
- Demo Version

I also, in my git (although this would be the same for svn and others I guess) two branches. the master branch is for production and the demo branch is for the presentation / demo version.

Currently in my setup I have the whole repository associated with the parent project.

My Application -----------------------> SOFTWARE REPOSITORY git
- Production Version
- Demo Version

What I would love to be able to do is change is to that I can associated the sub-projects with individual branches in my repositories, for example.

My Application
- Production Version ----------------> SOFTWARE REPOSITORY git master branch (svn trunk)
- Demo Version ----------------------> SOFTWARE REPOSITORY git demo branch (an svn branch)

Related issues

Related to Redmine - Defect #7984: Confusing revisions links on repository root New 2011-03-24
Related to Redmine - Feature #7246: Handle "named branch" for mercurial Closed 2011-01-07
Related to Redmine - Feature #1311: Subversion: Show revision histories for branches New 2008-05-27

Also available in: Atom PDF