Commit b38537d
authored
ci: sign automated release-update commits (#183)
## What
Add `sign-commits: true` to the `peter-evans/create-pull-request` step
in `.github/workflows/update-releases.yml`.
## Why
The workflow currently commits via the action's default local-git path,
which produces **unsigned** commits. Branch protection on `main`
requires *"commits must have verified signatures"*, so the automated PRs
it opens (e.g. #182) cannot be merged:
```
committer: github-actions[bot]
verified: false
reason: unsigned
```
With `sign-commits: true`, `create-pull-request` builds the commit
through the GitHub git-data API. Commits created via the API with
`GITHUB_TOKEN` are signed server-side by GitHub and show as **Verified**
(attributed to `github-actions[bot]`), satisfying the requirement. No
key management needed.
## Notes
- Committer identity on generated commits becomes `github-actions[bot]`
rather than the local git config — expected with API-created commits.
- Applies to future runs. The already-open #182 can be regenerated by
re-dispatching this workflow once merged (fixed branch name +
`delete-branch: true` updates the PR in place).
Refs #168.
---------
Signed-off-by: Terry Howe <terrylhowe@gmail.com>1 parent 6f3b32c commit b38537d
1 file changed
Lines changed: 11 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
68 | 68 | | |
69 | 69 | | |
70 | 70 | | |
| 71 | + | |
71 | 72 | | |
72 | 73 | | |
73 | 74 | | |
74 | | - | |
| 75 | + | |
| 76 | + | |
75 | 77 | | |
76 | | - | |
77 | | - | |
78 | | - | |
79 | | - | |
| 78 | + | |
| 79 | + | |
| 80 | + | |
| 81 | + | |
| 82 | + | |
| 83 | + | |
| 84 | + | |
| 85 | + | |
80 | 86 | | |
81 | 87 | | |
82 | 88 | | |
0 commit comments