Skip to content

Document external pull requests contribution policy - #454

Merged
anisaoshafi merged 2 commits into
mainfrom
pro-260-community-contribution-readiness
Aug 19, 2026
Merged

Document external pull requests contribution policy#454
anisaoshafi merged 2 commits into
mainfrom
pro-260-community-contribution-readiness

Conversation

@gtsiolis

@gtsiolis gtsiolis commented Aug 12, 2026

Copy link
Copy Markdown
Member

Motivation

The repository restricted pull request creation to collaborators, but its contribution guide still told external contributors to fork the repository and open a PR. That directed people toward a workflow they could not complete and did not clearly explain how they could participate instead.

Solution

Clarifies the contribution policy in README and CONTRIBUTING:

  • States that outside pull requests are not accepted
  • Directs external participation toward well-formed issues
  • Asks for reproducible bug reports and problem-focused feature requests
  • Explains why outside patches are not currently accepted
  • Restricts the pull request instructions to authorized collaborators
  • Removes the stale instruction to fork the repository

This PR does not add issue forms or templates. The existing issue-submission flow remains unchanged.

The following related work remains out of scope:

  • Establishing a private security-reporting path
  • Cleaning up unused contribution labels
Docs

Nothing to document elsewhere. This PR updates the repository README and CONTRIBUTING guide; the lstk documentation site has no contribution section.

Review

Human review advised: this changes the user-facing participation policy presented on the repository's front door.

Towards PRO-260

Co-Authored-By: Claude noreply@anthropic.com

@gtsiolis
gtsiolis requested review from a team and peter-smith-phd as code owners August 12, 2026 17:13
@gtsiolis gtsiolis added semver: patch docs: skip Pull request does not require documentation changes labels Aug 12, 2026
@gtsiolis gtsiolis self-assigned this Aug 12, 2026
@gtsiolis
gtsiolis force-pushed the pro-260-community-contribution-readiness branch from f55ceb5 to b04e7f1 Compare August 12, 2026 17:15
@gtsiolis

Copy link
Copy Markdown
Member Author

Cc @anisaoshafi because of relevant discussion.

Comment thread README.md Outdated
@gtsiolis
gtsiolis force-pushed the pro-260-community-contribution-readiness branch 4 times, most recently from c4dda86 to f3c282b Compare August 19, 2026 07:07
gtsiolis and others added 2 commits August 19, 2026 21:04
Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Claude <noreply@anthropic.com>
@gtsiolis
gtsiolis force-pushed the pro-260-community-contribution-readiness branch from f3c282b to 2ca7af3 Compare August 19, 2026 18:14
@gtsiolis

Copy link
Copy Markdown
Member Author

Added 2ca7af3 with a section to explain why we don't accept external contributions. Cc @anisaoshafi

@gtsiolis
gtsiolis requested a review from anisaoshafi August 19, 2026 18:15

@anisaoshafi anisaoshafi left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks George for bringing clarity and for the considerate reasoning. Appreciate how you keep these docs up-to-date. Couldn't have expressed it better 馃檶馃徏

@anisaoshafi
anisaoshafi merged commit 89c32cd into main Aug 19, 2026
19 checks passed
@anisaoshafi
anisaoshafi deleted the pro-260-community-contribution-readiness branch August 19, 2026 19:50

Copy link
Copy Markdown
Member Author

Thanks for merging, @anisaoshafi and thanks for reviewing, @tiurin! 馃弨


Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs: skip Pull request does not require documentation changes semver: patch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants