Skip to content

Preserve CI pull_request trigger from Fern regeneration - #96

Merged
paul-paliychuk merged 1 commit into
mainfrom
fix/preserve-ci-pull-request-trigger
Jul 28, 2026
Merged

Preserve CI pull_request trigger from Fern regeneration#96
paul-paliychuk merged 1 commit into
mainfrom
fix/preserve-ci-pull-request-trigger

Conversation

@paul-paliychuk

Copy link
Copy Markdown
Contributor

Summary

  • Restore pull_request (and push to main) on .github/workflows/ci.yml so PR checks run again.
  • Add .github to .fernignore so Fern regeneration cannot overwrite release CI (matching the Python and TypeScript SDKs).
  • Bump actions/setup-go to v5 while restoring the prior automation-ready CI shape.

Why

The Fern Go generator emits on: [push] only. The v3.25.0 regeneration overwrote the hand-maintained CI trigger, so subsequent releases fail a readiness check that requires pull_request.

Test plan

  • Confirm CI runs on this PR (compile + test).
  • Confirm .fernignore contains a .github line.
  • After merge, close or refresh any open Fern regen PR that still rewrites ci.yml without the ignore (e.g. SDK regeneration #95), so a merge cannot reintroduce on: [push].

Made with Cursor

Fern's Go generator rewrites .github/workflows/ci.yml to on: [push] only.
Ignore .github and restore pull_request so PR checks keep running.

Co-authored-by: Cursor <cursoragent@cursor.com>
@paul-paliychuk
paul-paliychuk merged commit 09f4533 into main Jul 28, 2026
7 checks passed
@paul-paliychuk
paul-paliychuk deleted the fix/preserve-ci-pull-request-trigger branch July 28, 2026 19:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant