Not standardized. Read (internal) Formatting & Linting.
We use a modifed version of GitFlow.
- "feature branches" have a specific prefix:
feat/for features and updatesfix/for bugfixes and hotfixesrefactor/for large internal changeschore/for no-op changesdocs/for documentationperf/for performance improvementstest/for test case updates- or other "types" from Conventional Commits
- "develop" branch is usually
main,
but can exist as a long-lived multi-feature branch prefixed withdev/ - "release branches" (as needed) are prefixed with
release/ - "hotfix branches" are prefixed
fix/ - "master branch" is always
main
Our development site is always up-to-date with main branch.
Note The development site is only accessible behind the TACC Network.
Our production site is built from a specific commit.
- Create release and tag on GitHub.
- Build & Deploy off of
vN.N.N.