Skip to content

Instantly share code, notes, and snippets.

View zacharyabresch's full-sized avatar
💭
loving Clojure & Datomic.

Zachary Abresch zacharyabresch

💭
loving Clojure & Datomic.
View GitHub Profile
@zacharyabresch
zacharyabresch / deleting-branches.md
Last active April 12, 2018 16:36
Proposal for branch deletion process & workflow

Deleting Branches After Merging

Recently, I completed a pull request and merged my branch into staging once approved. In the past, I've seen some developers delete their branch after merging and others don't do this. I've historically been pretty bad at this myself and was wondering what the team thinks about this.

Personal Opinion

I think that deleting branches after a successful merge should be a practice followed by everyone on the team. There are a lot of good reasons to do [this][1] and there's really no reason not to, IMHO. Currently, on staging, there are 229 branches! (git branch --all | wc -l) Of those 229, 69 of them show as "merged" (git branch --all --merged | wc -l). Running git branch --all is far less useful in this state.