Repository navigation
Add pull-request CI and require green checks - #3
Merged
Merged
Conversation
Introduce a Check workflow on pull_request and main that runs the same canonical pnpm check and test:all gate used by trusted publish, so merges can require a green status. Extend the post-publish npm visibility wait from 120s to 360s after v0.2.0's registry lag failed provenance verify.
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
.github/workflows/check.ymlso PRs andmainrun the samepnpm check+pnpm test:allgate as the publish package-gate.mainwill require thecheckstatus (configured viagh).Test plan
checkjob is green on this PRmainbranch protection requirescheckMade with Cursor