Repository navigation
Fixes #446: Clarify contribution approval labels in the docs - #449
Merged
Merged
Conversation
rohanmalhotracodes
requested review from
bhaveshpatel640,
chiragjn,
debajyoti-truefoundry,
heerambavi1998,
sr07asthana and
thesujai
as code owners
August 26, 2026 13:46
|
chiragjn
approved these changes
Aug 26, 2026
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
Clarifies how repository labels relate to the maintainer approval process for community code contributions.
Closes #446
Changes
help-wantedissues are open to community contributions.needs-maintainer-approvalissues should not be implemented until reviewed.How was this tested?
pnpm prettier --check CONTRIBUTING.md.git diff --check.Checklist
pnpm build,pnpm test,pnpm typecheck,pnpm lint:ci, andpnpm format:checkpass locallypackages/trueforge-sdk,.github/fern/openapi/openapi.json,docs/openapi.json) — fork PRs omit SDK regen; maintainers regenerate after merge.env.exampleupdated if configuration or behavior changedNote
Low Risk
Documentation-only change to contribution guidelines; no runtime or security impact.
Overview
Updates CONTRIBUTING.md so contributors understand when maintainer approval is required and how GitHub issue labels map to that process.
The important callout now says to open PRs for an issue only after a maintainer has approved work, not just “don’t submit PRs without approval” in the abstract. A new tip explains that new issues are labeled
needs-maintainer-attentionby default (matching the issue templates), that maintainers will triage them, and that contributors should not remove that label.A new Issue labels table documents
help-wanted(community code welcome) versusneeds-maintainer-attention(discuss with maintainers before implementing). Closes #446.Reviewed by Cursor Bugbot for commit 23092be. Bugbot is set up for automated code reviews on this repo. Configure here.