Within the gitbranchhealth directory, the following results are shown:
refs/remotes/origin/issue-1: 1 week ago
refs/remotes/origin/issue-7: 1 week ago
refs/remotes/origin/issue-5: 6 days ago
refs/remotes/origin/issue-2: 5 days ago
refs/remotes/origin/issue-3: 2 days ago
refs/remotes/origin/issue-14: 2 days ago
refs/remotes/origin/issue-6: 2 days ago
refs/remotes/origin/issue-9: 6 minutes ago
Because of the passed-in -D option, the branches origin/issue-1 and origin/issue-7 should be removed. They aren't, however.
This issue covers the following tasks:
Add debug output to determine why the deletion isn't working.
Add unit tests to cover branch deletion
Refactor the branch code to contain deletion, in support of the above unit tests
Add some type of user communication to ensure branches are deleted (at least an acknowledgement that this has happened, but preferably some type of switch to confirm that it should take place, with an override, perhaps -f, --force).
Right now, when the following command is run:
Within the gitbranchhealth directory, the following results are shown:
Because of the passed-in
-D
option, the branches origin/issue-1 and origin/issue-7 should be removed. They aren't, however.This issue covers the following tasks:
-f, --force
).