All code that lands on master is auto deployed to the staging environment.

All code on the prod branch is auto deployed to production via GCP Cloud Build.

These are based on work in different areas. There is design, back end, and front end (more will be added). The boards are set ip kanban style with automated progression based on the tickets state.

Issues are for bugs, features, or just tasks. All work needs to be tracked in an issue.

Issues have flags to sort what they are related to, such as design, enhancment etc.

The person the issue is assigned to is responsible for the work of the issue

All PRs are to target master. No PR can target prod except from master.

Each PR must have 1 reviewer that is not the person writing the code.

These people are responsible for merging the card and any ops work needed for the card to land. This person can not be the person the wrote the code.

Please use the appropriate labs for the PR. They are used to explain what the PR will relate to.

This sets the PR to the proper Kanban board.

These must be set to keep track of current milestone progress.