3 ms·
What does your daily Git workflow look like? I'm curious how other engineers manage their Git setup and workflows in practice. Specifically: 1. Primary Git cl
by bmf-san 1y ago
What does your daily Git workflow look like?
I'm curious how other engineers manage their Git setup and workflows in practice. Specifically:
1. Primary Git client: Do you mostly use the CLI, a GUI tool, IDE integration, or custom scripts? And why?
2. Workflow shortcuts: Do you follow the classic `git add → commit → push` step-by-step, or do you bundle them into a single alias or script?
3. Interactive tasks: How do you handle more interactive tasks like staging hunks, resolving conflicts, or browsing history?
4. Alias and script maintenance: If you maintain custom aliases or functions, how do you keep them organized and shareable?
I’d love to hear what works for you (and what didn’t). Tools, habits, setups — anything goes!
- mvieira38 1y ago1- mostly CLI but I'll use VSCode for merge editing, I think it's very nice 2- no aliases, I want to be aware of every step 3- for browsing history I'll go to Github (at my current job), I think it's a more pleasant experience 4- I don't apply
- sonkajarvi 1y ago1. CLI 2. I have two aliases: gs for "git status", and gap for "git add -p" 3. I use VSCode for resolving conflicts, and GitHub or gitk for browsing history 4. No maintenance. I add them by hand if they're missing