Document external pull requests contribution policy - #454
Open
gtsiolis wants to merge 1 commit into
Open
Conversation
gtsiolis
added
semver: patch
docs: skip
Co-Authored-By: Claude <noreply@anthropic.com>
gtsiolis
force-pushed
the
pro-260-community-contribution-readiness
branch
from
August 12, 2026 17:15
f55ceb5 to
b04e7f1
Compare
Member
Author
|
Cc @anisaoshafi because of relevant discussion. |
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.
Motivation
Pull request creation is now restricted to collaborators (
pull_request_creation_policy = collaborators_only), but the repo still tells external contributors to fork and open a PR — CONTRIBUTING's first PR step is literally "Fork the repository". Someone following it hits a wall with no explanation.Solution
States the policy in CONTRIBUTING and README, and keeps the channel that is still open visible: issues, which is the external channel that actually gets used (3 of our 6 issues came from outside, versus 2 fork PRs in 446). Also drops the stale fork step, which was already wrong for us — everyone branches directly.
The wording says "not currently", so reopening later doesn't need a retraction.
Two follow-ups this deliberately leaves out:
SECURITY.mdhere or inlocalstack/.github, so a reporter's only route is a public issue. Adding one needs the admin toggle enabled andsecurity@localstack.cloudconfirmed as an inbound mailbox first.good first issueandhelp wantedhave 0 uses ever and are not in the synced manifest, so they can be deleted.community contributionshould stay — feat(config): add LogDir and move diagnostic logs to XDG state #192 and Add doctor command for environment checks #184 carry it.Docs
Nothing to document. The change is to the repository's own CONTRIBUTING and README; the lstk docs site has no contributing section.
Review
Please review. This is user-facing policy text on the repo's front door, and the contribution policy was going to be raised at Monday's DevX sync — worth landing the wording with the team rather than self-merging.
Towards PRO-260
Co-Authored-By: Claude noreply@anthropic.com