Archiving changes (and viewing them)

[avamsi]

I sometimes have these changes that I'm not quite ready to discard but at the same time, I don't want them in my log as well.

I started "tagging" these changes manually with #jj-archive (i.e., put this somewhere in the description) and excluding them from my log revset (with archived = 'description(substring:"#jj-archive")') -- this kind of does what I wanted to do and I can easily view my archived changes with jj log -r archived.

1. Does anyone else have similar workflows? Do you do something different?
2. Is there a way to simplify the "tagging" part? Ideally this would be a single jj alias called archive (I think the --trailer flag from FR: add "signed-off-by" line #1399 (comment) would help)?

[avamsi]

For posterity, I've since added aliases in my jjconfig to make this easier (avamsi/dotfiles#10 (comment)).

[steveklabnik]

Is there a way to simplify the "tagging" part?

Sounds like topics, to me, I think? #3402

[avamsi]

Yep, thanks -- that does seem aligned!

[alycda]

For anyone who lands here: I opened #10268, a feature request for a first-class jj hide / jj unhide covering this use case. It would hide changes without tagging their descriptions, which rewrites them, and would work in tools that don't read revsets.log. It links a small prototype and the edge cases it ran into: merges where only one parent is hidden, and ordering between hidden sets.