docs: contributor workflow — CONTRIBUTING, PR template, maintainer review guide - #45
Merged
Conversation
…iew guide) - CONTRIBUTING.md: PRs base on staging; staging -> main at publish time, maintainer-only, always a merge commit; dev commands incl. per-file wallet tests; fork-PR CI expectations; SECURITY.md link. - PULL_REQUEST_TEMPLATE.md: what/why, testing, breaking changes, staging base checkbox. - REVIEWING.md: maintainer safety flow for external PRs (diff-first read, red flags, claim verification, isolated-worktree gates, prove new tests fail without the fix, pull_request_target ban).
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
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.
Part of setting up the contributor workflow (feat -> staging -> main).
What
staging;staging->mainhappens at SDK publish time, maintainer-only, always a merge commit; dev setup and per-file wallet test commands; what fork contributors should expect from CI; SECURITY.md link.Testing
Docs only — no code changes.