chore(ci): add PR build check (foundation for auto-merge)#14
Merged
Conversation
…o-merge) The docs repo only had a deploy-on-merge workflow, no PR-blocking CI. This adds a `CI` workflow that runs `bun run build` (which includes Next.js TypeScript checking and MDX compilation) on every PR to main. The resulting `Build` status check is what branch protection on main will require, which in turn is what `allow_auto_merge` will wait for. Without this gate, auto-merge would land PRs the moment they're created. Style matches the existing `nextjs.yml` deploy workflow (unpinned action versions, simple Bun setup). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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
Adds a CI workflow that runs
bun run buildon every PR to main. This is the foundation for enabling branch protection + auto-merge on this repo: the resultingBuildstatus check is what protection will require, and whatallow_auto_mergewill wait for.bun run buildinvokesnext buildwhich runs TypeScript checking, MDX compilation, and static page generation — covers the same ground I've been verifying manually before opening doc PRs (kinetic rewrite, audit sync, etc.).Style matches the existing
nextjs.ymldeploy workflow (Bun, unpinned action versions, similar cache shape).Next steps after merge
mainrequiring theBuildcheck (viagh api).allow_auto_mergeon the repo (currentlyfalse).gh pr merge --auto --squashand will land once the build passes.Test plan
bun run buildpasses locally (used this same command for every recent docs PR)🤖 Generated with Claude Code