4 ms·
Thank you for proving my point. What you really want to do is git commit -anm "wip" The -a is important because maybe you haven't staged the changes yet. Th
by underdeserver 2y ago
Thank you for proving my point.
What you really want to do is
git commit -anm "wip"
The -a is important because maybe you haven't staged the changes yet.
The -n is important because otherwise your pre-commit hooks will run, and potentially modify your commit.
Also, what happens if some of the files were partially staged?
- motorest 2y ago> What you really want to do is No. I only need to run hit commit. The rest is just silly attempts to nitpick your way to faking complexity where there is none. You don't need to pass --all because you should know and tell what changes go into the commit. You don't need or care to skip precommit hooks, because either you don't have any or you have them and you want to run them. That's it. Also, even your attempt to make a mountain out of a molehill ends up with a easier, smaller command line entry.
- TheBicPen 2y agoI have no horse in this race but it seems to me that you're not understanding their point. JJ has a different workflow that doesn't have a concept of a staging area, for one. The fact that you don't need to make a WIP commit may not be a game-changer for you, but it demonstrates that the abstractions it provides more accurately represent the "editing a previous commit" workflow. If that's not useful to you, fine. But I think it's valuable to have tools that 1) integrate into existing (git-based) systems with low friction and 2) provide abstractions more suitable for the work I tend to do on a daily basis.