Do we want a commit hook that rejects badly named branches?

[fpdotmonkey]

With tetrabiodistributed/tetra#50, we have a standard for branch names, i.e. [issue label]/[hyphen seperated description]-[issue number]. Do we want a commit hook that screams when someone makes a badly named branch?

[fpdotmonkey]

things for this:

• enforcing convention is good
• it can be used to clearly convey what the convention is when developers care

[fpdotmonkey]

things against this:

• I'm (at least for now) the only developer. I can probably maintain convention on my own
• I'm told this kind of commit hook is annoying

[capsulecorplab]

I was going to say... I think a commit hook would work for developers pushing via CLI, but idk if it also works on the GitHub UI - where I suspect people would be more inclined to break convention.

[fpdotmonkey]

You might be able to add a pre-commit hook to the repo on github's servers, maybe something like scp pre-commit git@github.com:tetrabiodistributed/project-tetra-display/.git/hooks, but that's hacky as heck. Anyway branch naming might be better socially enforced.