3 ms·
Mostly, I'm comfortable with the git CLI workflow (of course, I have often worked as a "lead" before, as well). However, we do use gitk at my current job to vi
by Roboprog 12y ago
Mostly, I'm comfortable with the git CLI workflow (of course, I have often worked as a "lead" before, as well). However, we do use gitk at my current job to visualize the change history tree of a project.
Tools like gitk need a mode to auto-sync their visualization (BUT NOT your workspace) with the "origin", so you can quickly see what is going on in the outside world, as well as your own work, just like you would see in a centralized system. I wonder if gitk has a --show-origin flag or some such thing that I missed?
It's nice to be able to work off-line, but most of us at the end of the day are part of a work-group all trying to complete something together, and need to see the centralized view of project status/history.
- taeric 12y agoFor that, I have come to prefer a 'git fetch' workflow over a 'git pull' based one. I don't know what change that will cause in gitk, but otherwise it does basically what you are asking for.
- Roboprog 12y agoThanks, I will have to check out using "fetch" next week. I'm not sure what happens if I do a fetch while my workspace already has "master" checked out, but if I have a local working branch checked out, this looks like a safe way to peek ahead at what others are doing before I blindly start merging/pulling.