What is jj and why should I care?

Re:What is jj and why should I care? by qezz on Tuesday April 14, 2026 @09:46AM (#47765609)

For those, who want to/need to keep some files uncommitted, the workaround I found is to put gitignore into some nested directory:

  mkdir junk
  echo '*' > junk/.gitignore

jj won't track those files under ./junk/

Also might be relevant for claude, since it wants to put its settings into the repo itself as `.claude/`:

  mkdir junk/.claude
  bwrap ... --bind "$(pwd)/junk/.claude" "$(pwd)/.claude" ...

For some more common files, I use global gitignore file as

  # ~/.gitconfig
  [core]
    excludesFile = ~/gitconf/gitignore_global

  # ~/gitconf/gitignore_global
  .envrc
  .direnv/*

[ Parent | on HN ]

Re:What is jj and why should I care? by BeetleB on Tuesday April 14, 2026 @11:32AM (#47766987)

You can also set snapshot.auto-track to tell it not to track certain files.

Another option is to make a branch with the files that you want to keep around but not push (e.g. stuff specific to your own tooling/editor/IDE), and mark that branch as private. Private commits (and their descendants) can't be pushed.

You then make a merge commit with this branch and main, make your changes, etc. You will have to rebase before pushing so that your branch isn't a descendant of the private commit.

This will involve more work, but it has the benefit that you're actually version controlling your other files.

[ Parent | on HN ]

Re:What is jj and why should I care? by tcoff91 on Tuesday April 14, 2026 @10:33AM (#47766188)

I run jj in colocated mode so I put stuff in .git/info/exclude if I want it ignored but not part of the main .gitignore

[ Parent | on HN ]