4 ms·
Personally, I find these aliases a bit too terse. Aliases are important for enhanced productivity, but shell aliases are too much. I find these git aliases muc
by yuvadam 15y ago
Personally, I find these aliases a bit too terse.
Aliases are important for enhanced productivity, but shell aliases are too much. I find these git aliases much more comfortable:
alias.st=status
alias.co=checkout
alias.com=checkout master
alias.cam=commit -a -m
alias.cm=commit -m
alias.br=branch
push, pull, merge, rebase and the rest are infrequently used, so I don't alias them at all. Using shell aliases (as opposed to git aliases) is unjustified IMO, as is the horrible
alias g='git'
which gives me the creeps.
- pdelgallego 15y agojust another one alias grm="git status | grep deleted | awk '{print \$3}' | xargs git rm"
- sanderjd 15y agoWhy do shell aliases make you uncomfortable? If we are talking about your personal machine, and not a server where another user can be bitten by not understanding your personal alias preferences, what could the harm be?
- basman 15y agoI use the g=git alias :) Are there any negative consequences I should be aware of?
- Terhorst 15y agoTab-completion via git-completion.bash won't work. I think you can add the following at the end of git-completion.bash to fix it, though: complete -o bashdefault -o default -o nospace -F _git g 2>/dev/null \ || complete -o default -o nospace -F _git g
- philwelch 15y agoTab-completion on my zsh setup still works. I'm not sure why.
- sid0 15y agoMercurial accepts unique prefixes to commands by default. (For example, hg me is the same as hg merge.) Hg wins again!
- Pistos2 15y agoI quite agree. Here are my git aliases: stat = status stta = status satt = status tat = status co = checkout fo = fetch origin ff = merge --ff-only ffo = merge --ff-only @{u} po = push origin HEAD