Skip to content

Automate spec drift response: open regen PR instead of issue#55

Open
natestemen wants to merge 1 commit into
mainfrom
automate-spec-drift-pr
Open

Automate spec drift response: open regen PR instead of issue#55
natestemen wants to merge 1 commit into
mainfrom
automate-spec-drift-pr

Conversation

@natestemen
Copy link
Copy Markdown

@natestemen natestemen commented Jun 2, 2026

Summary

  • Replaces the spec-drift issue workflow with one that automatically fetches the new spec, regenerates the client, and opens a PR
  • The generated PR targets spec-drift/auto-regen branch, requests review from ionq/developer-tools, and carries the spec diff in a collapsible section
  • If a drift PR is already open, subsequent weekly runs update its body rather than opening a duplicate

Test plan

  • Confirm ionq/developer-tools is the correct team slug for review requests
  • Trigger via workflow_dispatch once merged to verify the happy path (no drift → no PR; drift → PR opened)
  • Verify the spec-drift label exists in the repo (needed for --label spec-drift to succeed)

🤖 Generated with Claude Code

When upstream OpenAPI spec diverges, fetch the new spec, regenerate the
client, and open a PR assigned to ionq/developer-tools rather than
filing an issue for someone to do manually.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@natestemen natestemen requested a review from a team as a code owner June 2, 2026 04:53
@natestemen natestemen added the spec-drift Upstream OpenAPI spec has changed label Jun 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

spec-drift Upstream OpenAPI spec has changed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant