3 ms·
> When I create a commit, several things happen: > my staged files disappear from my list of file changes > a new commit is appended to my git log > my
by FeepingCreature 3y ago
> When I create a commit, several things happen:
> my staged files disappear from my list of file changes
> a new commit is appended to my git log
> my branch ends up with a new head commit, diverging from its upstream
> If you create a commit from the command line, you see none of this.
Sure, if you're not using an addon like powerline-shell. If you do, all of those are immediately obvious.
I'd argue it's less "commandline bad" and more "stock commandline bad."
- euroderf 3y agoThis is my problem with git. SO many moving parts to visualize. So on the topic of visualization, can someone make a simple(?) GUI tool that has all these entities, and sequentially animates some arrows, with annotations, showing just what the heck is going on ? Do it for the most commonly used commands but also for the rarely-used ones. And for every command that invokes it (presumably using a hook), then display OK/Cancel. Git training wheels. Meant to be abandoned once you get the hang of it.
- zeroimpl 3y agoPrecisely this. Most of my coworkers seem to use a prompt that just reports what branch you are on. I use a power line-based prompt that captures a lot more info, and so I virtually never end up in a situation where I forgot to include files or forgot to push my commit since it’s super obvious.