Release Workflow

Normally there will be 2 active branches in this repository: development and master, and depending on the status of ongoing development we will often open a 3rd release branch in order to prep a release (perform any regression testing, etc...).

We try to follow the popular GitFlow workflow: https://nvie.com/posts/a-successful-git-branching-model/

development ... to ... release ... to ... master

Each branch commit kicks off our CI/CD pipeline which is a GitHub Action, and the build is published to its respective Expo release channel.

GitHub Branch	Expo Release Channel
development	default
release	release
master	production

If a Production release also meets the criteria specified in Expo's Publishing Reference: https://docs.expo.io/workflow/publishing/ , then an OTA update will take place and we do not need to perform an App/Play Store release (unless we want to for sake of updated release notes, or screenshots, etc...).