Skip to content

Simple and efficient way to delete remote branches from git repository.

License

Notifications You must be signed in to change notification settings

hyperia-sk/remote-branch-housekeeping

Repository files navigation

GIT Remote Branch Housekeeping

Build Status codecov

git remote-branch-housekeeping is a simple and efficient way to delete remote (--merged or --no-merged) branches from git repository.

screenshot

Usage

git remote-branch-housekeeping
# or 
remote-branch-housekeeping

Parameters

remote-branch-housekeeping [ -f | -r | -d | -b | -n ]

-d <number>, --days <number>
Defines days, default 14.

-b <master>, --branch <master>
Branch name, default "master".

-r <origin>, --remote <origin>
Remote name, default "origin".

-n, --no-merged
Delete only branches that are not merged.

-f, --force
Don't ask for confirm to delete branches.

Installation

git clone https://github.com/hyperia-sk/remote-branch-housekeeping.git && cd remote-branch-housekeeping

Open up the cloned directory and run:

Unix like OS

sudo make install

For uninstalling

sudo make uninstall

For update/reinstall

sudo make reinstall

OS X (homebrew)

@todo

Windows (cygwin)

C:\cygwin\bin\bash installer.sh

For uninstalling

C:\cygwin\bin\bash uninstaller.sh

System requirements

  • Unix like OS with a proper shell
  • Tools we use: git ; perl ; grep ; sort ; sed ; head ; wc ; xargs ; date

Dependences

  • perl apt install perl

Contribution

Want to contribute? Great! First, read this page.

Code reviews

All submissions, including submissions by project members, require review. We use Github pull requests for this purpose.

Some tips for good pull requests:

  • Use our code When in doubt, try to stay true to the existing code of the project.
  • Write a descriptive commit message. What problem are you solving and what are the consequences? Where and what did you test? Some good tips: here and here.
  • If your PR consists of multiple commits which are successive improvements / fixes to your first commit, consider squashing them into a single commit (git rebase -i) such that your PR is a single commit on top of the current HEAD. This make reviewing the code so much easier, and our history more readable.

Formatting

This documentation is written using standard markdown syntax. Please submit your changes using the same syntax.

Tests

make test

Licensing

MIT see LICENSE for the full license text.