News for hackers. Stuff that matters.
Re:Jujutsu Primer by mirashii on Friday November 20, 2026 @09:10AM (#50574896)
Stage or no, git or jj, not writing a gitignore once and never worrying about removing hunks as you described or filtering the list of unstaged files in your brain for debug artifacts seems like completely unnecessary cognitive load. I’ve never come across a project that staunchly refuses to gitignore the paths of build artifacts that shouldn’t be checked in. It’s basic hygiene to prevent accidents. I really can’t understand any reason to oppose doing so.
Re:Jujutsu Primer by boltzmann64 on Friday November 20, 2026 @10:38AM (#50576322)
it only causes accident if you do git add --all. and my exact thesis is to be deliberate about what you commit.

`git add -e` your files as you are satisfied (of course after remove your debug harness). this way you debug harness stays put in your sandbox/worktree and no harness leaks into your project which remains pristine. this is something that .gitignore cannot do. jj cannot. you have remove all your harness, TODOs and others just to commit and then add it back again. that just means your version control failed.

and no, i am not advocating you should no add .gitignore.

Re:Jujutsu Primer by mirashii on Friday November 20, 2026 @10:50AM (#50576529)
> you have remove all your harness, TODOs and others just to commit and then add it back again

No, you don't. You can split. You can untrack. You can change your auto-track configuration. There are many ways to deal with this other than having to remove them. You can be equally deliberate about what goes into your final commit.