docs(chore): clarify focused validation commands#240
Open
tin-computer[bot] wants to merge 1 commit into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Summary: - Replace the raw validation command list with an annotated table. - Explain when each focused repository check is appropriate. Rationale: - Keep contributor guidance aligned with the package scripts and the documented validation contract. - Make the full release gate the unambiguous pre-shipping default. Tests: - git diff --check origin/dev...HEAD - docs-only review against package.json and AGENTS.md Co-authored-by: highoncomputers <261291146+highoncomputers@users.noreply.github.com>
Ducksss
force-pushed
the
codex/triage-contributor-proposals
branch
from
fe3cc9c to
c8b63b5
Compare
Ducksss
changed the title
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
pnpm test:releasethe clear pre-shipping defaultRationale
The README now matches the repository's package scripts and documented validation contract, so contributors can choose the smallest useful check while still knowing when the full release gate is required.
This carries forward the focused validation guidance originally proposed by @highoncomputers in #233 while keeping this PR documentation-only.
Validation
git diff --check origin/dev...HEADpackage.jsonandAGENTS.md