Christine Chen 186c1075ce fix: chain Speakeasy auto-merge into Generate run ...

The auto-merge workflow triggered on `pull_request: [labeled, opened]`.
When github-actions[bot] opened the regen PR, GitHub's recursion guard
refused to run a workflow triggered by another workflow's GITHUB_TOKEN,
so the run landed as action_required with zero jobs executed. Regen PRs
piled up unmerged and sdk_publish never fired (PyPI stuck at 0.10.0).

Port the TypeScript SDK's architecture: make auto-merge a workflow_call
reusable workflow chained inside the Generate run (generate ->
resolve-branch -> auto-merge). No separate pull_request-triggered run
exists, so there is nothing for GitHub to gate.

- auto-merge-speakeasy-pr.yaml: workflow_call inputs (run_started_at,
  branch_name) + App-token secrets; resolve PR via branch/timestamp;
  .author.is_bot check; wait_for_checks before direct merge; step
  summaries. Keeps the SHA-pinned create-github-app-token.
- sdk_generation.yaml / sdk_generation_for_spec_change.yaml: add
  concurrency group, resolve-branch + auto-merge jobs.

2026-06-25 16:08:16 -04:00

..

auto-merge-speakeasy-pr.yaml

fix: chain Speakeasy auto-merge into Generate run

2026-06-25 16:08:16 -04:00

notify-monorepo.yaml

feat: add monorepo sync notification workflow

2025-11-15 15:53:15 -05:00

sdk_generation_for_spec_change.yaml

fix: chain Speakeasy auto-merge into Generate run

2026-06-25 16:08:16 -04:00

sdk_generation.yaml

fix: chain Speakeasy auto-merge into Generate run

2026-06-25 16:08:16 -04:00

sdk_publish.yaml

wip setup

2025-11-13 13:40:55 -05:00