Coding since 11yo, that makes it over 30 years now ~~~
Have a PhD in Comp Sci ~~~
Love to go on bike tours ~~~
I try to stay as generalist as I can in this crazy wide place coding is at now.
I wish that the aliases in oh_my_zsh were commented to tell you what they do in plain english. I will often look in there and try to add a new one to my arsenal, but that becomes a bit of a research project since I'm not fluent in git commands and typically need to look things up, at least just to be sure that the commands will do what I suspect.
git add . is 'all commit' only if you have changes on the current path. If you have changes in e.g. sibling dir it won't work as you'd have to go up the path which is ... For a true 'all commit' use git add -A.
I like that - I have gc aliased to git commit so I'll usually do gc -am "commit message" but that does have the the drawback of not adding new files and I forget that 90% of the time and then have to amend the commit which is a whole thing.
Sometimes I code, always I write — A simple man making his way through the galaxy, writing as I go — 📚 Author of "Street-Smart Coding in the Age of AI": bit.ly/csarag-sscai
Location
Colombia 🇨🇴 (not Columbia)
Work
Content, Courses & Training for .NET teams — Helping teams to write maintainable & performant code
Principal Software Engineer at Red Hat Working on Ansible
Creator and Maintainer of dynaconf.com
Fellow Member of the Python Software Foundation
Aspiring Rustacean
🇧🇷 🇵🇹
Location
Viana do Castelo, Portugal
Education
Information Systems
Pronouns
he/him
Work
Principal Software Engineer at Red Hat for Ansible
A nice one is
For those times you were just too quick on the trigger, and want to add some additional staged files to your last commit.
Feel free to use a different alias, like
goopsorgredo🤨I've been meaning to add one like this - thinking
gcraporgdoh, or maybe justgc!I use this to set
git lgto be a cleaner overview of history:Results in a nice tree view of history showing authors, hashes, titles and the tag/branch names.
That's a good one.
I must say that I never goes beyond the aliases that are by default in zsh and oh_my_zsh.
Here is a quick extract of the aliases available in oh_my_zsh :
I wish that the aliases in
oh_my_zshwere commented to tell you what they do in plain english. I will often look in there and try to add a new one to my arsenal, but that becomes a bit of a research project since I'm not fluent ingitcommands and typically need to look things up, at least just to be sure that the commands will do what I suspect.One of my fav aliases I always set up in git's own aliasing config is:
git acFor git "all commit". Which is an alias for
git add .; git commit -m.To just add & commit everything in one go.
git add .is 'all commit' only if you have changes on the current path. If you have changes in e.g. sibling dir it won't work as you'd have to go up the path which is... For a true 'all commit' usegit add -A.Thanks!
I do always run this from project root so I'm ok. But I think I'll switch to your suggestion! :)
I like that - I have
gcaliased togit commitso I'll usually dogc -am "commit message"but that does have the the drawback of not adding new files and I forget that 90% of the time and then have to amend the commit which is a whole thing.Today I came across to this one:
alias gconf='git diff --name-only --diff-filter=U'To list the conficted files after a merge
Here are the aliases I use gist.github.com/zivni/90a6a93fec67...
I use
huband I aliasgit=hubthen I have
git sync, git pr list, git pull-request create, git release etc...
I hadn't heard of
hub, will have to check it out.hub: A command-line tool that makes git easier to use with GitHub
Just created this little handy alias for interactive rebase