[wishlist] mark branch as inactive or hidden

Bug #767332 reported by Alexander Belchenko
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
bzr-colo
Fix Released
Wishlist
Unassigned

Bug Description

I'd like to have the ability to mark some arbitrary branches inside colo workspace as inactive or hidden, so they won't be shown in the output of colo-branches unless --all flag is specified. It could be useful if you don't want to delete every finished feature branch, but in the same time want to put them out of sight.

I see some possible ways to achieve this:

* Move inactive branches into special subdirectory, e.g. .bzr/branches/_INACTIVE. It could be simple enough to support and easy to manipulate from CLI

* Set the special option in branch.conf of those branches, e.g. `colo_inactive = True` and analyze all found branches for this option. It could be more bzr-way, but could be slower and requires special way to manipulate this value from command-line (maybe new `bzr config` command might help here).

Related branches

Changed in bzr-colo:
status: New → Confirmed
importance: Undecided → Wishlist
Revision history for this message
Neil Martinsen-Burrell (nmb) wrote :

I'd rather not have to add colo-specific information to the branch.conf. I am leaning towards a convention for which branches not to show in colo-branches. I am leaning towards hiding branches whose name starts with "." as with the unix ls command. There could then be a --all option to show those branches. This will also allow those who wish to use a directory such as ".inactive" if they want to keep all of their inactive branches in one place.

Can you let me know if that would be a satisfactory way to address this request?

Revision history for this message
Alexander Belchenko (bialix) wrote : Re: [Bug 767332] Re: [wishlist] mark branch as inactive or hidden

Neil Martinsen-Burrell пишет:
> I'd rather not have to add colo-specific information to the branch.conf.
> I am leaning towards a convention for which branches not to show in
> colo-branches. I am leaning towards hiding branches whose name starts
> with "." as with the unix ls command. There could then be a --all
> option to show those branches. This will also allow those who wish to
> use a directory such as ".inactive" if they want to keep all of their
> inactive branches in one place.
>
> Can you let me know if that would be a satisfactory way to address this
> request?

That will be OK. And I think it will be good start. Thank you.

--
All the dude wanted was his rug back

Revision history for this message
Martin Pool (mbp) wrote :

I wonder if changing the name will cause other things in bzr that
refer to the branch to break. Perhaps we can add a branch_status
configuration option to the branch.conf that is not colo-specific?

Martin

Changed in bzr-colo:
status: Confirmed → Fix Released
Revision history for this message
Neil Martinsen-Burrell (nmb) wrote :

Good point Martin. I've pushed the version where renames are used for hiding, but I'm interested if there would be interest in a sort of advisory field for the status of a branch. Now that we have "bzr config", there is an easy way to change that sort of metadata from the UI, so it wouldn't have to be special-cased for bzr-colo. I will ask on the list if there are other parts of the Bazaar ecosystem that would be interested in using a branch_status flag.

Revision history for this message
Alexander Belchenko (bialix) wrote :

I'm not sure is it intended behavior now:

C:\work\Bazaar\plugins\qbzr>bzr colo-branches
  0.19
  0.20
  experimental/.hidden
* trunk

C:\work\Bazaar\plugins\qbzr>bzr colo-branches --all
  .hidden
  0.19
  0.20
  experimental/.hidden
* trunk

So .dotnames in subdirectories does not treat as hidden?

Revision history for this message
Alexander Belchenko (bialix) wrote :
Revision history for this message
Neil Martinsen-Burrell (nmb) wrote :

see bug 774170 for the desire to hide a branch without renaming it

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.