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
+17Lines changed: 17 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -144,3 +144,20 @@ Please contact us for specific advice, but in outline this generally involves:
144
144
## Monitoring and logging
145
145
146
146
Please see the [monitoring-and-logging.README.md](docs/monitoring-and-logging.README.md) for details.
147
+
148
+
## CI/CD automation
149
+
150
+
A GitHub Actions workflow which checks for new upstream version release tags and updates the downstream repo, can be found at:
151
+
152
+
.github/workflows/upgrade-check.yml.sample
153
+
154
+
If activated, the workflow is scheduled by default to run every day at 9 AM UTC and can be triggered manually via the `workflow_dispatch` event. How to activate the workflow is detailed at the top of the file.
155
+
156
+
In order for GitHub actions to fetch workflow changes in `.github/workflows`, a PAT for each deployment must be provided.
157
+
158
+
The following repository permissions must be set for the PAT:
159
+
-`Workflows : Read and write`
160
+
-`Actions : Read and write`
161
+
-`Pull requests: Read and write`
162
+
163
+
The PAT should then be copied into a downstream repo secret with the title `WORKFLOW_TOKEN`.
0 commit comments