Closed OkazakiTokkatsu closed 2 years ago
Thanks for giving me a good feature request. I will check a little more to see if this change has any negative impact.
I thought pruning was also good for the purpose of this tool to clean up.
I would proceed with the following policy:
With --dry-run
: Do not pruning
Without --dry-run
: git remote prune
after removing branches (git fetch --prune
includes getting remote-tracking branches, so we will proceed without fetch)
Description
I would like the tracking branch
(remotes/origin/****)
removed at the same time.Steps to reproduce
Ensure that the merged branch remains.
Run gh-poi
Ensure that the tracking branch remains in place.
Run prune
Now, all branches was cleaned!
Perhaps the prune executed here should be done by gh-poi. (The above command may not be sufficient to avoid gh-poi deleting tracking branches other than the one you deleted.)
Additional context
gh version 2.14.3 (2022-07-26) gh poi seachicken/gh-poi v0.5.6