> There are already loads of branches within this repository, which can/will > lead to further confusion,
Those look like "feature branches" -- which can be "pruned" once they are no longer needed. https://railsware.com/blog/2014/08/11/git-housekeeping-tutorial-clean-up-outdated-branches-in-local-and-remote-repositories/ Note that if a branch has been merged, then pruning that branch doesn't lose any information in the history. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/130#issuecomment-412939772
