A good API is like a Mozart symphony. If you hit all the right notes and read the correct rhythm, the magic of music will happen.
Branching is a core concept in Git, and the entire GitHub Flow is based upon it. There's only one rule: anything in the master branch is always deployable.
Because of this, it's extremely important that your new branch is created off of master when working on a feature or a fix. Your branch name should be descriptive (e.g., refactor-authentication, user-content-cache-key, make-retina-avatars), so that others can see what is being worked on. from github guides
#### prefered naming prefix
- new-feature
- new-section
- new-page
- update
- upgrade
- fix
- amend
- refactor
- remove
- About Naming
Naming is hard! Don't underestimate the time necessary to design a good contract. Especially since the names you choose will stay forever - remember, GraphQL APIs have no versions, they evoluate. Also, try to make your schema self explanatory, because it's the first piece of code that new developers will read. from Dive Into GraphQL Part III