|
3 | 3 | # newer tag is found in the upstream repository then a pull request is created to the downstream repo
|
4 | 4 | # in order to merge in the changes from the new upstream release.
|
5 | 5 |
|
6 |
| -# To use this workflow in a downstream azimuth-config repository simply copy it into .github/workflows |
7 |
| -# and give it an appropriate name, e.g. |
8 |
| -# cp .github-upgrade-check.yml.sample .github/workflows/upgrade-check.yml |
| 6 | +# To use this workflow in a downstream azimuth-config repository, first copy it into .github/workflows |
| 7 | +# and give it an appropriate name, e.g. `cp .github-upgrade-check.yml.sample .github/workflows/upgrade-check.yml` |
| 8 | +# then create a fine-grained GitHub access token for the target repository with the permissions specified here: |
| 9 | +# https://github.com/peter-evans/create-pull-request?tab=readme-ov-file#token |
| 10 | +# (i.e. contents: write, pull-requests: write AND workflows: write). |
| 11 | +# GitHub actions can be funny about using tokens with no expiry date in workflows so make sure the token |
| 12 | +# has an expiry date. After creating the token, copy the generated secret string and set it as a GitHub |
| 13 | +# actions secret named WORKFLOW_TOKEN in the repository's settings page. |
9 | 14 |
|
10 | 15 | name: Check for upstream updates
|
11 | 16 | on:
|
@@ -58,11 +63,12 @@ jobs:
|
58 | 63 |
|
59 | 64 | - name: Create Pull Request
|
60 | 65 | if: ${{ steps.release_tag.outputs.value }}
|
61 |
| - uses: peter-evans/create-pull-request@v6 |
| 66 | + uses: peter-evans/create-pull-request@v7 |
62 | 67 | with:
|
63 | 68 | base: main
|
64 | 69 | branch: ${{ steps.branch_name.outputs.value }}
|
65 | 70 | title: "Upgrade Azimuth to ${{ steps.release_tag.outputs.value }}"
|
66 | 71 | body: This PR was automatically generated by GitHub Actions.
|
67 | 72 | commit-message: "Upgrade Azimuth to ${{ steps.release_tag.outputs.value }}"
|
68 | 73 | delete-branch: true
|
| 74 | + token: ${{ secrets.WORKFLOW_TOKEN }} |
0 commit comments