Replace spec-drift issues with an auto-merging weekly regeneration PR - #101
Open
splch wants to merge 3 commits into
Open
Replace spec-drift issues with an auto-merging weekly regeneration PR#101splch wants to merge 3 commits into
splch wants to merge 3 commits into
Conversation
There was a problem hiding this comment.
Pull request overview
Replaces issue-based spec drift reporting with automated client regeneration and merging.
Changes:
- Adds weekly spec synchronization and regeneration.
- Adds octo-sts authentication policy.
- Updates documentation and removes the previous drift workflow.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/spec-sync.yml |
Creates, validates, and merges regeneration PRs. |
.github/workflows/spec-drift.yml |
Removes issue-based drift reporting. |
.github/chainguard/spec-sync.sts.yaml |
Grants scoped automation permissions. |
CONTRIBUTING.md |
Documents automated synchronization. |
AGENTS.md |
Updates workflow guidance. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
antalszava
self-requested a review
September 2, 2026 09:40
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
spec-drift.yml(weekly issue) withspec-sync.yml: on drift it re-vendorsopenapi.json, regenerates the client, opens aspec-drift-labeled PR carrying the spec diff, and squash-merges once all required checks pass.del(.info.description), Fix spec-drift false positives from date-only description changes #49); regeneration matchesgenerated.yml, so the requiredstalenesscheck verifies every sync PR.self-modifypattern (trust policy in.github/chainguard/, no stored secrets); the merge relies on the octo-sts App's PR-only bypass of themainruleset (one-time settings change, applied separately).First run after merge picks up the drift tracked in #89.
Test plan
uvx zizmoranduvx pre-commit runpass locally with no new findings.gh workflow run spec-sync.yml, confirm the sync PR opens with the diff and self-merges once checks pass.Important
Most code in
ionq_core/is auto-generated and overwritten on regeneration.See CONTRIBUTING.md for which files are safe to edit.