Describe the issue / feature in 1-2 sentences:
Too many branches without descriptions
Background
We have many feature branches needed for dev environment & CI-related tasks. Need docs to explain the purpose of each branch.
Details
<tjz8659> I won't push anything there. You should update the README for those nightly branches just so you and others know what the nightly branches are there for
<ctmartin> Too lazy for now, yell at me at the meeting next week
<tjz8659> Lol okay. I'm doing some work now
<jwf> Big +1 to documenting this
<ctmartin> I think using feature branches more liberally would be nice, and using a wiki page to document those since it's not write-protected. Also, changing the README.md files in each branch will mean we need to make a commit to undo that before it gets merged, I'd rather not do that.
<jwf> Oh, I misunderstood what Tim typed. I don't think the README should be different in each branch, but in the README, there should be a brief line that explains what other, permanent branches there are and what they are.
<jwf> It should be documented somewhere.
<ctmartin> I still vote wiki b/c branch protection
<jwf> Reasons like this are why I don't like multiple branches :P
<jwf> But the`devel` branch shows up anyways, right?
<jwf> Why does branch protection matter, actually?
<ctmartin> jwf: b/c it matters when your unit test pulls from the repo and thus you can't try a fix unless you put it there
<ctmartin>Also, according to the graphic on the the Git SCM website, it's normal
<axk4545> what did I miss??
<ctmartin> axk4545: jwf was arguing against sane development
<jwf> You don't leave much room for a rebuttal :P
ct-martin
commented
6 years ago
Summary
Background
We have many feature branches needed for dev environment & CI-related tasks. Need docs to explain the purpose of each branch.
Details