Add non-blocking CI checks for pull requests - #6
Merged
Merged
Conversation
Run ESLint, internal link/asset checks, and a full static build on every PR targeting main. Mirrors the contributor workflow in docs/pull-request-workflow.md and the environment in deploy.yml (Node 22). These are reported on the PR but are not required status checks, so they surface problems without blocking merges. Co-Authored-By: Claude Opus 4.8 (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
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 lightweight CI workflow that runs on every PR targeting
main:npm run lint(ESLint)npm run lint:links(internal reference + public asset integrity)npm run build(full static export)It mirrors the checks contributors already run locally (
docs/pull-request-workflow.md) and the environment indeploy.yml(Node 22,npm ci).Why
Gives real, automated feedback on PRs — catching broken profile JSON, missing images, dead internal links, and build breakage before merge.
Not strict on purpose
These are not configured as required status checks, so they report pass/fail on the PR but never block a merge. Can be promoted to a required gate later if desired.
🤖 Generated with Claude Code