Skip to main content

Git Flow & Versioning

The current flow mimics the setup from Assemble Web.

  • A staging branch that receives short-lived feature/fix branches
  • A main branch that receives changes from merging the staging branch into it.

The versioning is automated through Github Actions, and tied to push listeners to both these branches.

Additionally, the app handles 2 versions: one for the web/hosted code (elevate/ folder), and another for the native/Electron code (electron/ folder).

Deploy Actions​

Staging Validations​

  • This action fires through cron, at 9:00 AM and 3:00 PM EST
    • Can be fired manually
  • Runs validations and test cases
  • Increases the version to a pre-release (ie. dev suffix)
    • This applies to both web or electron versioning
  • Deploys the changes to Accedo Staging (HP TV+)

Main Validations​

  • This action fires on push event
    • Can be fired manually
  • Promotes the pre-release version (ie. remove the dev suffix)
    • This applies to both web or electron versioning
  • Deploys the changes to Accedo Production (HP TV+)
  • Pushes the changes to the HP Repository
warning

Always confirm that the actions ended successfully.