Search results
@samebchaseSamuel Chase yup, that is how I've always been working, and now I get it for free. Can't believe I don't even miss magit so far.
@vedangVedang Manerikar I still work with the various commercial forges as if I'm using Gerrit. Lots of rebasing, fixups etc. like the good old days 😉.
Tried using #jj a month ago. It seemed fine, but I am not confident that I can safely use it with repos at work. I want to avoid a situation where I do something silly and it ends up being confusing/broken for everyone. I want to reach "being able to get unstuck using the reflog" level of familiarity with jj, and then I will be able to use it regularly for work.
In other news: https://github.com/9999years/git-prole has been working beautifully for me. I think I'll need something like jj-prole to make things completely seamless. Not sure if jj has the same issues with remotes, that git-prole is trying to solve.
A few days with #jj and not looking back
this is jj btw: https://jj-vcs.github.io/jj/latest/
think of it as "the rust of vcs" — annoying but game-changing
@fasterthanlimeamos
Things that I really wish #git had (and IIUC #jj is good at this):
- an undo command that can undo any git commands including those whom destroyed uncommited state like `git restore uncommited/file`
- `git bisect --rebase-original-branch` or whatever that would make it easy to commit a fix after a bisect (generaly I want to amend the falty commit then rebase the original branch on top of it).
- `git commit --fixup-and-rebase` instead of manually having to do an interactive rebase