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: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,9 +10,9 @@ When you want to use this GitHub Action your GitHub repository should have a `de
10
10
should use tags for
11
11
releases.
12
12
13
-
- For the `dev` branch we will change the files specified under `gitops-dev`.
14
-
- For the `master` / `main` branch we will change the files specified under `gitops-stage`.
15
-
- For a new tag the files under `gitops-prod` will be used.
13
+
- For the `dev` branch we will change the files specified under `gitops-dev`. These changes are committed to the `dev` branch of the GitOps repository.
14
+
- For the `master` / `main` branch we will change the files specified under `gitops-stage`. These changes are committed to the default branch (`main`) of the GitOps repository.
15
+
- For a new tag the files under `gitops-prod` will be used. These changes are committed to the default branch (`main`) of the GitOps repository.
16
16
17
17
This GitOps setup should be the default for all your repositories. However, if you have a special case, you can
18
18
leave `gitops-dev`, `gitops-stage` and `gitops-prod` undefined, then those steps will be skipped.
0 commit comments