Development process

Step 1: Create a Branch

Before you make any changes, ensure you're working on a new branch off the latest main branch of the project. This keeps the main branch clean and your changes organized. This branch should follow the following convention:

Branch convention:

  1. Should use the Ticket ID (as a prefix) from the Notion ticket you are working on. This allows us to track it back to the project tracking tool.
  2. Use a small description to give an idea on what the branch is doing.
  3. Use a suffix to indicate if its a defect, feature or documentation.

All the above to be separated by a -. Example of it all together below.

git checkout -b [TOTA-XXX]-[small-description]-[feature/docs/defect]

Branch examples:

git checkout -b TOTA-349-demo-experience-feature
git checkout -b TOTA-364-gut-testing-docs
git checkout -b TOTA-363-new-day-defect