git git git git git
alexmolas
41 points
19 comments
August 18, 2026
Related Discussions
Found 5 related stories in 56.9ms across 4,128 title embeddings via pgvector HNSW
- Git at Any Scale meetpateltech · 30 pts · August 18, 2026 · 64% similar
- The Git history command deserves more attention turbocon · 179 pts · July 14, 2026 · 55% similar
- GitRoot ilreb · 13 pts · July 18, 2026 · 54% similar
- OpenAI Forked Git on GitHub rahlokzero · 23 pts · July 11, 2026 · 53% similar
- Git worktrees are not an isolation boundary for coding agents alchaplinsky · 31 pts · July 30, 2026 · 49% similar
Discussion Highlights (13 comments)
ggm
Do the exec() tail call?
3stacks
Its a weird feeling to see something posted on here and remembering it being posted nearly 10 years ago I think of this every time I write git git status
sshine
I never have this exact problem. It's rare that my stale prompt has a "git" in it. Most of my git commands have mnemonic aliases like "gs", "gd", "gl". I usually have the problem where a stale "ls" or "vim" inhabits the prompt.
modeless
I need one called "gits" that accepts a command "tatus".
philipallstar
> See what other git alias’ I have This should be "aliases".
Subdivide8452
Never had this, but I kinda wanna add the alias just in case now
roli64
So this is what people do with their spare time.
docheinestages
Would it work with "giggity" too?
tempfile
It's amazing the lengths people go to in order to avoid typing more carefully.
walrus01
Buffalo Buffalo buffalo Buffalo buffalo?
skrebbel
I recommend also adding this: [alias] really = !exec git This solves the common situation where you could’ve sworn you pushed your worl, but colleague can’t find it regardless. You can then `git really push` to be sure.
quietlathe
The exec matters here. Without it each extra git would stack another shell process.
VCFundedGenYer
Weirdly specific issue exclusive to the author.