WIP and private commits

Sometimes I do not know what I am building yet.

I still commit.

Not because the work is done, but because I want to make the idea durable. Once it is a commit, I can move it, compare it, abandon it, rebase it, or come back to it later.

jj diff
jj commit -m "wip: try stacked push flow"

If the work is not meant for review, I mark it more clearly:

jj commit -m "private: notes from debugging auth callback"

Keep private commits off the remote

Once I started using private: as a real parking lot, I wanted one extra guardrail: if I ever try to push those commits, jj should refuse.

This config does that:

[git]
private-commits = "subject('private:*')"

With that set, jj git push refuses to push commits whose subject matches private:*. It also refuses to push descendants that would require pushing the private commit.

The command-line form is:

jj config set --user git.private-commits "'''subject('private:*')'''"

The nested quotes are only there so the revset quotes survive the shell.

I leave wip: pushable because sometimes the whole point of a WIP commit is to get CI or a teammate’s eyes on it. private: is the stronger word in my vocabulary.

Find the messy stuff later

Because I use a prefix, I can search for these commits later:

jj log -r 'subject("wip:*")'
jj log -r 'subject("private:*")'

That searches all visible history, so it can return old commits from other people too.

Most of the time I only want WIP commits in my current stack. For that, I intersect the subject search with trunk()..@:

jj log -r 'subject("wip:*") & trunk()..@'
jj log -r 'subject("private:*") & trunk()..@'

In my config, those stack-scoped searches are:

jj wip
jj private

When a WIP commit is ready to become a real change, see Promoting a WIP commit.