ObsidianHome/07 - GameDevSpace/Processes/Git CICD.md

tags, relates-to, creation-date, modification-date

tags	relates-to	creation-date	modification-date
note/permanent devops/cicd		2024-04-09 09:46	Tuesday 9th April 2024 09:49:48

Git CI/CD

Compass

[!multi-column]

[!info]+ Comes from Somewhere

[!success]+ Similar to Something

[!danger]+ Competes with Something

[!seealso]+ Leads to Somewhere

Core

In a trunk based game development environment, here's a list of the basic actions taken to make the game go through the whole CI/CD process.

CI

• MANUAL: create a branch from main to code something
• MANUAL: commit and push to this branch
• AUTO: build the game, run the game (null hypothesis test)
• AUTO: run basic tests (unit/functional), any test that can be done quickly in a matter of minutes max.
• AUTO: on success, create a PR.
• AUTO: labelling: feat, fix, chore, docs, code-review. If labeled as code-review, let it sit.
• AUTO: otherwise, merge to main and delete current branch

CD

• AUTO: merging a PR on main bumps

---

References