actions/fluxcd-flux2
3
0
Fork 0
mirror of https://github.com/fluxcd/flux2.git synced 2026-02-22 15:41:47 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

improve the introduction

Browse source 
It did not say effectively what you should get out of reading this
document in the first paragraph.

Signed-off-by: Kingdon Barrett <kingdon@weave.works>
This commit is contained in:
Kingdon Barrett 2021-04-26 14:33:05 -04:00
parent 85b3eeb87b
commit a6e25ed99b
No known key found for this signature in database
GPG key ID: 470B0A4ACF2A4E23
1 changed files with 4 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/use-cases/gh-actions-auto-pr.md
View file

@ -1,8 +1,10 @@
# GitHub Actions Auto PR
In the [Image Update Guide] we saw we can [Push updates to a different branch] by using `.spec.git.push.branch` to push image updates to a different branch than the one used for checkout.
This guide shows how to configure GitHub Actions to open a pull request whenever a selected branch is pushed.
In this example, we configure an `ImageUpdateAutomation` resource to push to a `staging` branch, (which we could set up separately as a preview environment to deploy automatic updates in a staging cluster or namespace.)
In the [Image Update Guide] we saw that Flux's automation can [Push updates to a different branch] by using `.spec.git.push.branch` to push automated image updates to a different branch than the one used for checkout.
In this example, we configure an `ImageUpdateAutomation` resource to push to a `staging` branch, where we can imagine some policy dictates that updates must be staged and approved before they are deployed in production.
```yaml
kind: ImageUpdateAutomation