project.cfg: can we make component option BRANCHES optional?
Bug #313654 reported by
Alexander Belchenko
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ScmProj plugin |
Fix Released
|
Wishlist
|
Alexander Belchenko | ||
Bug Description
In some situations there is one and only one branch for some components. Therefore BRANCH_URL should not contain any template variables, and BRANCHES option is simply redundant. We can make it optional therefore, but just need to provide some checks.
To create local branch copy we need branch name though. It could be auto-generated based on last part of BRANCH_URL as usual behaviour for bzr branch command.
| description: | updated |
| Changed in bzr-scmproj: | |
| importance: | Undecided → Wishlist |
| status: | New → Confirmed |
Revision history for this message
| Alexander Belchenko (bialix) wrote | #1 |
| Changed in bzr-scmproj: | |
| assignee: | nobody → bialix |
| milestone: | none → 0.4.5 |
| status: | Confirmed → Fix Committed |
| Changed in bzr-scmproj: | |
| milestone: | 0.4.5 → 0.4.5a1 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Implemented in format-change branch as part of new format refactoring.