Manage Git branches that you might no longer need.
Ruby
Switch branches/tags
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
bin
lib
spec/lib/git_arbor
.document
.gitignore
.rspec
Gemfile
LICENSE.txt
README.rdoc
Rakefile
VERSION
git-arbor.gemspec

README.rdoc

git-arbor

Git Arbor will help identify Git branches you no longer need. It does so by looking at the last commit from each branch. If a branch has no commits in the past 180 days, Git Arbor lets you know about it.

Contributing to git-arbor

  • Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet.

  • Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it.

  • Fork the project.

  • Start a feature/bugfix branch.

  • Commit and push until you are happy with your contribution.

  • Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.

  • Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.

Copyright

Copyright © 2012-2013 SciMed Solutions. See LICENSE.txt for further details.