rkh/rbenv-update — pull request #17 by jasonkarns (2014-11-14 15:16:32+00:00)
Title: respect repository and branch names

Respect the currently checked out branch, and just pull from the configured remote for the current branch.

Currently rbenv-update is making a lot of assumptions:

1) that you have a branch named `master`
2) that you have a remote named `origin`
3) that `master` is the branch you *want* to be using
4) that `origin` is the remote you *want* to be using (this precludes using forks - unless the fork is named `origin`...)

The repository and branch arguments are optional. Doing a simple `git pull` will remain on the currently checked out branch, and will use the configured remote for the current branch. This allows the user to remain in control of branch names, remote names, active branch, and use forks if they so choose.