| ▲ | saghm 11 hours ago | |||||||||||||||||||
The idiom here is use `edit` if you want to edit a commit, and use `new` if you want to make a new commit. This works identically whether you specify the commit via branch name or commit id. I'm not sure why people are saying not to use `edit` ever. It's basically just a shorthand for staging and amending changes in an existing commit, and there's still a use case for that; it's just not "I want to see the changes on this old branch". | ||||||||||||||||||||
| ▲ | embedding-shape 11 hours ago | parent | next [-] | |||||||||||||||||||
> Just don't ever use `edit`, > The idiom here is use `edit` if you want to edit a commit You know, you guys have fun with that, I'll continue using git which (probably) has the same amount of warts, but I already know them. I'll continue to refer new VCS users to jj, seems a lot easier to learn, but really don't have the interest to re-learn a bunch of ever-changing idioms. | ||||||||||||||||||||
| ||||||||||||||||||||
| ▲ | joshuamorton 10 hours ago | parent | prev [-] | |||||||||||||||||||
I think it's because it's easy to make annoying mistakes (still easy to fix with undo) with edit. And it gains relatively little over new+squash. Edit is a useful power-feature, but I think for a novice, "never use it, only use the more well understood workflow of new+squash" is a good heuristic. | ||||||||||||||||||||