Git Branch Naming

These are my personal rules for naming Git branches.

1. Use all lowercase characters separating words by dashes (-), no underscores (_)
2. Include GitHub issue number at the end (or Jira issue key at the beginning)
3. Optional branch type prefix (e.g. feat, fix, chore) separated by a forward slash (/)
4. Optional initials prefix (e.g. sf) separated by a forward slash (/), these branches may have history rewritten

Example Branch Names

• add-current-temp-endpoint-17
• ic-1287-add-current-temp-endpoint
• feat/add-current-temp-endpoint-17
• sf/feat/add-current-temp-endpoint-17
• sf/feat/ic-1287-add-current-temp-endpoint

Sal Ferrarello (@salcode)

Sal is a PHP developer with a focus on the WordPress platform. He is a conference speaker with a background including Piano Player, Radio DJ, Magician/Juggler, Beach Photographer, and High School Math Teacher. Sal can be found professionally at WebDevStudios, where he works as a senior backend engineer.