Commit 8e5bac5
authored
fix(ci): use RELEASE_PLZ_TOKEN in checkout action to trigger workflows (#132)
## Summary
This PR fixes the release-plz workflow failure that occurred after PR
#131 was merged. The previous approach of replacing `GITHUB_TOKEN` with
`RELEASE_PLZ_TOKEN` in the env section caused the release-plz action to
fail because its internal git-config step expects `GITHUB_TOKEN` to be
set.
## Solution
This fix uses a different approach: the `RELEASE_PLZ_TOKEN` is now used
in the checkout action's `token` parameter. This allows:
- The checkout to use the PAT (Personal Access Token) which can trigger
other workflows
- The release-plz action to still have access to `GITHUB_TOKEN` for its
internal operations
## Changes
- Added `token: ${{ secrets.RELEASE_PLZ_TOKEN }}` to both checkout steps
in the release-plz workflow
- Kept the original `GITHUB_TOKEN` in the env section unchanged
This should properly trigger CI workflows on release-plz PRs while
maintaining compatibility with the release-plz action.
Fixes #1301 parent 90f2fa4 commit 8e5bac5
1 file changed
+4
-2
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
23 | 23 | | |
24 | 24 | | |
25 | 25 | | |
| 26 | + | |
26 | 27 | | |
27 | 28 | | |
28 | 29 | | |
29 | 30 | | |
30 | 31 | | |
31 | 32 | | |
32 | 33 | | |
33 | | - | |
| 34 | + | |
34 | 35 | | |
35 | 36 | | |
36 | 37 | | |
| |||
49 | 50 | | |
50 | 51 | | |
51 | 52 | | |
| 53 | + | |
52 | 54 | | |
53 | 55 | | |
54 | 56 | | |
55 | 57 | | |
56 | 58 | | |
57 | 59 | | |
58 | 60 | | |
59 | | - | |
| 61 | + | |
60 | 62 | | |
0 commit comments