Repository navigation
chore: add prep sync changesets with gh API put - #479
Conversation
- Change the `Commit changeset(s)` step in the `ai-prep-sync-pr` to use the gh API to put each changeset individually. This results in the commits created by the PR to be signed.
|
Schema Diff vs Published Schemas
No schema changes detected between local build output and published GitHub Pages schemas. |
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
The new logic silently ignores tracked changeset modifications and deletions.
Get a fresh assessment by requesting another Copilot review.
Review effort: Balanced
Findings: 1
Open (1)
What changed in this PR
Replaces local changeset commits with GitHub Contents API calls so commits are signed.
Changes:
- Uploads each detected changeset individually.
- Targets the PR head branch with base64-encoded content.
| File | Description |
|---|---|
.github/workflows/ai-prep-sync-pr.yml |
Replaces local commit/push logic with API uploads. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
kevinmia
left a comment
kevinmia
left a comment
There was a problem hiding this comment.
lgtm! Just left a minor, non-blocking comment
pnpm run changesetto create a changeset. |
Commit changeset(s)step in theai-prep-sync-prto use the gh API to put each changeset individually. This results in the commits created by the PR to be signed.I went with this approach because there's usually just a few changesets and this seemed simpler than pulling in another action to do the commit. Additionally, I couldn't find any widely-used actions for creating signed commits using the API (and as a result, not requiring GPG key management).
Should fix the failure first seen in #478