Command-line tool to delete merged Git branches
Project description
git-delete-merged-branches
A convenient command-line tool helping you keep repositories clean.
Installation
pip install git-delete-merged-branches
Example
# git-delete-merged-branches
You are about to delete 6 local branch(es):
- improve-setup-py
- issue-12-enable-ci-for-pull-requests
- issue-5-fix-waste-of-one-second-per-service
- keep-github-actions-up-to-date
- refactoring-one
- simple-ci
Delete? [y/N] y
You are about to delete 6 remote branch(es):
- origin/improve-setup-py
- origin/issue-12-enable-ci-for-pull-requests
- origin/issue-5-fix-waste-of-one-second-per-service
- origin/keep-github-actions-up-to-date
- origin/refactoring-one
- origin/simple-ci
Delete? [y/N] y
To github.com:hartwork/wait-for-it.git
- [deleted] improve-setup-py
- [deleted] issue-12-enable-ci-for-pull-requests
- [deleted] issue-5-fix-waste-of-one-second-per-service
- [deleted] keep-github-actions-up-to-date
- [deleted] refactoring-one
- [deleted] simple-ci
Features
- Supports deletion of both local and remote branches
- Supports workflows with multiple release branches, e.g. only delete branches that have been merged to all of
master,devandstaging - Quick interactive configuration
- Provider agnostic: Works with GitHub, GitLab and any other Git hosting
- Takes safety seriously
Safety
Deletion is a sharp knife that requires care.
While git reflog would have your back in most cases,
git-delete-merged-branches takes safety seriously.
Here's what git-delete-merged-branches does for your safety:
- No branches are deleted without confirmation or passing
--yes. - Confirmation defaults to "no"; plain
[Enter]/[Return]does not delete. git pushis used with--force-with-leaseso if the server and you have a different understanding of that branch, it is not deleted.- There is no use of
os.systemor shell code to go wrong. - With
--dry-runyou can get a feel for the changes thatgit-delete-merged-brancheswould be making to your branches. - Show any Git commands run using
--verbose.
Best Practices
When the repository is a fork (with an upstream remote and a fork remote):
- Make sure that release branches are tracking the right remote,
e.g.
mastershould probably track original upstream'smasterrather thanmasterof your fork. - Consider keeping your fork's remote
masterup to date (usinggit push).
Support
Please report any bugs that you find.
Like this tool? Support it with a star!
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
File details
Details for the file git-delete-merged-branches-2.0.1.tar.gz.
File metadata
- Download URL: git-delete-merged-branches-2.0.1.tar.gz
- Upload date:
- Size: 11.0 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/46.4.0 requests-toolbelt/0.9.1 tqdm/4.48.0 CPython/3.7.8
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | ec00f5e0fa3b9c2ae6de79233e28624ed218a3530b788e9b6224214085ccaa07 |
|
| MD5 | 7997ecb784e000bda89acaa384d0b960 |
|
| BLAKE2b-256 | 514a43cc32d91ef9f2cf929dd5e745245e78bf2e12c757b1d946e4307ca9f5e7 |
File details
Details for the file git_delete_merged_branches-2.0.1-py3-none-any.whl.
File metadata
- Download URL: git_delete_merged_branches-2.0.1-py3-none-any.whl
- Upload date:
- Size: 13.5 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/46.4.0 requests-toolbelt/0.9.1 tqdm/4.48.0 CPython/3.7.8
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | 8b118c7afa4b96e8985c2223637e11461f6ebb7033760f9c1056eaa797098c89 |
|
| MD5 | af9c384d21278440ff9291d7095842fb |
|
| BLAKE2b-256 | 581e63741c1fb76fa088bd529d6facc673c0a1f8dd025ba359630976c632cca7 |
