The problem
From time to time if you have many forks and do many pull requests it is inevitable that you will have stale branches. And as time marches on the number of these branches across forks can become big.
The answer
git-wipe is simple command line tool to cleanup your Github fork branches.
Install
$ pip install git-wipe
Usage
In order to use git-wipe first you need to create your Personal Access Token.
You can set this token to your environment variable:
$ export GIT_WIPE_TOKEN=your_access_token
And then you can easily:
$ git-wipe cleanup Searching for branches. This may take a while... Founded branches: povils/repo_1/Branch_1 povils/repo_1/Branch_2 povils/repo_2/Branch_1 povils/repo_3/Branch_1 Total: 4 Delete these branches? [y/N]: y
Other options
--token instead of environment --preview just to preview merged branches --timeout set connection timeout. Default 30 seconds --skip-repository skip repository you don't want to search. Multiple --skip-branch skip branch you don't want to delete. Multiple --no-interaction do not ask any interactive question
Example:
$ git-wipe cleanup --skip-repository=repo_1 --skip-branch=develop --no-interaction
This command will clean all merged branches without interaction, except from fork with name ‘repo_1’ and except all branches with name ‘develop’
Note:
Only forks where you are owner will be involved in search. Also master branches will never be deleted!
Metadata
Release files for git-wipe 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| git-wipe-0.1.2.tar.gz | 3.9 kB | Details |
Release files / git-wipe-0.1.2.tar.gz
| Download URL | git-wipe-0.1.2.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
143c2ee976bd16dfc77764d2e9f2a579438c0cf5b989b7e9748bd05ce2b46fb5
|
|
BLAKE2b-256 checksum How to use checksums |
443ccdf460f7429204b6c6d9177d015b4a9d3ff80145ca3058b738ff19702215
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |