1476005 - Docs Request for tree maintenance

Status: RESOLVED WONTFIX

(Developer Services :: General, task)

Description

[Matthew Gaudet (he/him) [:mgaudet]]

Currently mozilla-version-control-tools has a pretty good document describing a set of productive mercurial workflows [1]. 

However, I find this is missing the final part of the patch lifecycle, which is how to clean the tree of abandoned commits, experiments, mistakes, etc. ie, should I be marking these changesets as obsolete, `strip`ping them, etc? 

In git some of this happens naturally through GC; if a branch is deleted, you need to work hard to find those commits, and eventually they'd get GC'd. 

But I find that `hg wip` is slowly getting worse for me as my repo accumulates cruft, and I don't have a reliable mechanism for hiding no longer useful heads and commits. 



[1]: https://github.com/mozilla/version-control-tools/blob/ed9e12bb870d3f32d645f560e7a87b55d602affc/docs/hgmozilla/workflows.rst

Comment 1

[Matthew Gaudet (he/him) [:mgaudet]]

(the command I am looking for documentation on turns out to be |hg prune|)

Comment 2

[Connor Sheehan [:sheehan]]

`hg prune` is likely what you want (I use it all the time), however I believe it is dependent on the presence of the `evolve` extension.

It might be worth adding a new section on what an evolve-centric workflow looks like to make people aware of all the awesome commands it offers. Especially since we offer to install it via `./mach vcs-setup` (aka configwizard [1]).

Comment 3

[Connor Sheehan [:sheehan]]

(I <ENTER>ed too early, oops.) 

[1] https://hg.mozilla.org/hgcustom/version-control-tools/file/tip/hgext/configwizard/__init__.py#l800