$ cat ~/.bashrc | grep git
alias gitc='git commit -a -s'
alias gitls='git log --pretty=oneline'
alias gitb='git branch'
alias gitca='git commit -a --amend'
alias gits='git status' $ cat ~/.alias
alias g='git'
$ cat ~/.gitconfig
[alias]
st = status
br = branch
co = checkout
I don't see anyone else doing g='git' but I don't have to write out an alias for each command. For less frequently used git commands I forget an [alias] shortcut but I can always use the 'g' shortcut. # Complete aliased git, too.
complete -o default -o nospace -F _git g $ cat ~/.bash_profile | grep git
alias gco="git checkout"
alias gpu="git pull"
alias gcom="git commit"
alias gfr="git fetch && git rebase -i"
alias g="git"unlike the hub command by github(doing different things) the gem dependencies/parsley are not trivial to combine into a single standalone version, so if i chose to use this i would have to install this weird structure of a ruby gem that is distributed as some kind of app that installs itself into usr/lib(most probably because rubygems would make the startup time even slower).
apparently there's also this https://github.com/rtomayko/git-sh which is just bash. but yeah i think i'll just stick with my aliases and tig.
EDIT: i don't know how i saw a /usr/bin/ruby shebang, but forget that part of the rant
But perhaps we're getting a little bit carried away here, for a couple of keystrokes :-)
If you're on OS X, and installed via Homebrew, then the installer should have detected that system Ruby was too old and installed Ruby 2.0 from Homebrew for you.
If you're not on OS X, you'll need to either install Ruby 2.0 or later before installing gitsh, or if you want to work around our RVM avoidance, you can force the installer to use your current RVM Ruby: `RUBY=$(which ruby) ./configure`
I wrote an introduction to Magit a while back. Magit has a very simple and understandable "context menu" interface that gives you access to all of Git's functionality, and then some. In other words, it's not a pared-down environment like a lot of frontends.
http://www.masteringemacs.org/articles/2013/12/06/introducti...
Generally speaking, though, I love git because I don't have to break out from my normal flow to use it.
My use case is potentially very different since most of my projects under version control are personal / single_committer, but I've saved myself some of the typing by aliasing common git commands to short codes: 'git add' becomes 'ga', 'git commit' == 'gc', 'git push' == 'gp'. That way, committing/pushing a bug I've just fixed becomes `gc -am '$message' && gp`.
What might be interesting is being able to import and export configurations to standardize git usage across multi-coder projects?
ctrl+z and using other terminals is ok, but it's not the same thing.
Here is something like that for zsh in case you need it.
Of all the Git commands, I find myself using git status most often
I literally never use status. It's faster to use a shell prompt that displays uncommitted / untracked files.What about Windows?