When should you create a branch?

• When an issue is assigned to you (as long as it requires you make changes to the project).

What should the name of the branch be?

• The branch should start with the issue number, no hashtag.
• The branch should include the issue title, or a shortened version of it if it is too long.
• It should not include any capital letters.
• Each-word-should-be-separated-by-a-dash.
  • Example: 1337-write-coding-conventions

Important things to remember

• The branch should branch from the most recent branch of your team, not main.
• If an issue gets divided into smaller sub-issues during development, create new branches after merging the current, do not continue with the same branch.
• If an issue gets assigned to you shortly before merge-day, make sure you stash your changes (either manually or through Git) if you do not finish in time.
• Remember to switch to the newly created week branch.