Branch naming style

I propose that we have a development ("develop" or "dev") branch and master branch (the currently deployed version).

We can have other short-lived branches that follow this style:

{reason}-{1 to 3 word description}-{id-type}-{id}

Reasons would be limited to "bug", "feature", "refactor", "hotfix" or "spike" (spike for experiments).

So for example, to work on issue #23, I could name it "feature-add-lineup-selector-issue-23". Maybe that's a bit long. Should we try to limit the description to a word? Or always use issues (rather than stories, or other ids). So it could be "feature-lineup-23"

I'm going to set up CICD (Travis CI probably) on the project so I don't know if that matters for branch names other than for separating develop and master.