Contents

git-up
======

So `git pull` merges by default, when it [should really rebase](http://www.gitready.com/advanced/2009/02/11/pull-with-rebase.html). You can [ask it to rebase instead](http://d.strelau.net/post/47338904/git-pull-rebase-by-default), but it still won't touch anything other than the currently checked-out branch. If you're tracking a bunch of remote branches, you'll get non-fast-forward complaints next time you push.

Solve it once and for all:

![gem install git-up](http://dl.dropbox.com/u/166030/nonsense/git-up.png)

although
--------

`git-up` might mess up your branches, or set your chest hair on fire, or be racist to your cat, I don't know. It works for me.

configuration
-------------

`git-up` now has some configuration.  Yay.

As of `v0.4.1`, `git-up` can check your app for any new bundled gems and suggest a `bundle install` if necessary.

It slows the process down slightly, and is therefore enabled by setting `GIT_UP_BUNDLER_CHECK='true'` in your `.bashrc`, `.profile`, or whatever.

Version data entries

4 entries across 4 versions & 1 rubygems

Version	Path
git-up-0.4.4	README.md
git-up-0.4.3	README.md
git-up-0.4.2	README.md
git-up-0.4.1	README.md