@@ -20,21 +20,20 @@ jobs:
2020 uses : actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v4
2121 - name : scrape upstream and rewrite config.yaml
2222 run : python3 ./hack/build/refresh-nvidia-versions.py
23- - name : open PR if config.yaml changed
23+ - name : generate cultivator token
24+ uses : actions/create-github-app-token@1b10c78c7865c340bc4f6099eb2f838309f1e8c3 # v3.1.1
25+ id : generate-token
26+ with :
27+ app-id : " ${{ secrets.EDERA_CULTIVATION_APP_ID }}"
28+ private-key : " ${{ secrets.EDERA_CULTIVATION_APP_PRIVATE_KEY }}"
2429 # Uses the GitHub API path under the hood so commits are auto-signed
2530 # with the web-flow key (the repo enforces "Verified signatures", which
2631 # blocks plain `git push` from GITHUB_TOKEN). The action is idempotent:
2732 # repeated runs on the same branch update the existing PR.
28- #
29- # AUTO_PR_TOKEN, if configured as a PAT in repo secrets, lets the auto-PR
30- # trigger downstream `pull_request` workflows (the kernel build test).
31- # Without it we fall back to GITHUB_TOKEN, which can create the PR but
32- # will not allow CI jobs to autotrigger on PR open - a person still needs
33- # to kick over/close-reopen the PR to trigger CI.
34- # TODO bml generate and define a standalone token
33+ - name : open PR if config.yaml changed
3534 uses : peter-evans/create-pull-request@5f6978faf089d4d20b00c7766989d076bb2fc7f1 # v8.1.1
3635 with :
37- token : ${{ secrets.AUTO_PR_TOKEN || secrets.GITHUB_TOKEN }}
36+ token : ${{ steps.generate-token.outputs.token }}
3837 sign-commits : true
3938 branch : auto/refresh-nvidia
4039 base : main
0 commit comments