You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/architecture/deployment-pipeline.md
+20Lines changed: 20 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,3 +3,23 @@ title: Deployment Pipeline
3
3
parent: Architecture
4
4
nav_order: 5
5
5
---
6
+
7
+
## Exercises
8
+
9
+
Unit tests and [exercise configuration](/developers/docs/architecture/exercise-structure/#configuration-structure) will be run during the PR and every time a branch is merged into `main`.
10
+
11
+
These are controlled through the `CI` action on Github Actions ([here](https://github.com/git-mastery/exercises/actions/workflows/ci.yml)).
12
+
13
+
## Git-Mastery app
14
+
15
+
A new version of the Git-Mastery application is published when a new tag is pushed to `main`.
16
+
17
+
The versioning is done as follows: `<major>.<minor>.<patch>` where
18
+
19
+
1.`<major>`: for when major changes to the app occur (i.e. rewrites) where the application could break entirely
20
+
2.`<minor>`: for when critical bug fixes occur that users should be aware of
21
+
3.`<patch>`: for when minor bug fixes occur (i.e. cosmetic) that users don't need to update to
22
+
23
+
The app automatically checks for the latest version published and warns users if their local version is out of date if the `<major>` or `<minor>` versions are wrong.
24
+
25
+
If you do not have permissions to push a new tag, contact <woojiahao1234@gmail.com> for assistance.
0 commit comments