This repo contains some Git utility scripts. The highlights are git open
, git pull-request
, git push-branch
, and git undo
, which you'll never understand how you did without.
The commands are especially useful when combined with pivotal-github gem (which, despite its name, also works with Bitbucket).
The git-utils
used to be pure Bash scripts, but they are now available as a Ruby gem, both because Ruby is more powerful than bash and because now git-utils
can be included more easily as a dependency for the pivotal-github gem. As a result, installation is easy if you have RubyGems installed:
gem install git-utils
git amend
: alias forgit commit --amend
git anal
(use with caution): makes a commit with the message "Make anal changes"git cleanup
: deletes every branch already merged into current branch (apart frommaster
,staging
, anddevelopment
)git merge-branch [branch]
: merges current branch into given branch (defaults tomaster
)git open
: opens the remote page for the repo (OS X only)git polish
: makes a commit with the message "Polish"git pull-request
: pushes the branch and opens the remote page for issuing a new a pull request (OS X only)git push-branch
: pushes the current branch up to origingit delete-remote-branch <branch>
: deletes the remote branch if it is safe to do sogit switch <pattern>
: switches to the first branch matching the given patterngit sync
: syncs the local master with remotegit undo
: undoes the last commit
Here are some suggested aliases:
git config --global alias.mb merge-branch
git config --global alias.pr pull-request
git config --global alias.pb push-branch
Some of these commands deserve further explanation.
git merge-branch [target]
merges the current branch into the target branch (defaults to master
). On a branch called add-markdown-support
, git merge-branch
is equivalent to the following:
$ git checkout master
$ git merge --no-ff --log add-markdown-support
Note that this effectively changes the default merge behavior from fast-forward to no-fast-forward, which makes it possible to use git log
to see which of the commit objects together have implemented a feature on a particular branch. As noted in A successful Git branching model,
The
--no-ff
flag causes the merge to always create a new commit object, even if the merge could be performed with a fast-forward. This avoids losing information about the historical existence of a feature branch and groups together all commits that together added the feature… Yes, it will create a few more (empty) commit objects, but the gain is much bigger than that cost.
In addition, the --log
option puts the commit messages from the individual commits in the merge message, which is especially useful for viewing the full diff represented by the commit.
These options can be overriden (and thus restored to their defaults) by passing the options -ff
or --no-log
. git merge-branch
accepts any options valid for git merge
.
git push-branch
creates a remote branch at origin
with the name of the current branch:
$ git branch-push
* [new branch] add-markdown-support -> add-markdown-support
git push-branch
accepts any options valid for git push
.
git sync
syncs the local master
with the remote master
. On a branch called add-markdown-support
, git sync
is equivalent to the following:
$ git checkout master
$ git pull
$ git checkout add-markdown-support
The purpose of git sync
is to prepare the current branch for rebasing against master
:
$ git sync
$ git rebase master
(This is essentially equivalent to
$ git fetch
$ git rebase origin/master
but I don't like having master
and origin/master
be different since that means you have to remember to run git pull
on master
some time down the line.)
gem install git-utils