As far as I can tell, there is no tag command to easily share well-identified repository state, which is a necessary to tool to use pijul in the context of maintaining a software projects with releases and so on, at least to my opinion.

That’s totally true, and is due to the fact that I tried to reduce the number of commands. We need to talk about tags, especially now that there are version numbers (pijul log --states).

Tag as implemented in previous pijul’s versions (i.e., virtual change whose only purpose was to have the right dependencies) was a good way to deal with that. My understanding is that version numbers identify a state, but they don’t allow for “reconstructing” this state, right?

Wait, I was looking at this discussion yesterday, and then looked at pijul record again, and it seems this is already implemented: pijul record --tag. What is your opinion on that command?

@pmeunier

As far as I can tell, pijul record --tag does not appear to be comparable to git tag, but I could be missing something.

What would be like tags from Git would be if there were ‘read only’ channels that can be forked with pijul fork --channel <from> <to> but cannot be switched to with pijul channel switch <to>.

Side note: pijul record --tag is not supported anymore.

error: Found argument '--tag' which wasn't expected, or isn't valid in this context

If you tried to supply `--tag` as a PATTERN use `-- --tag`

USAGE:
    pijul record [FLAGS] [OPTIONS] [--] [prefixes]...

For more information try --help

This is the oldest feature request still open, and is about to be fixed. It’s required a full redesign of the backend engine, plus some extra tricks to compress databases, but it’s finally landed in main. Thanks to everyone involved, I’ll write a blog post soon to explain how it works.