You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Revising the contribution guidelines to encourage high-impact high-value contributions, which we find are typically creating issues, participating in issues and discussions.
Why
High-impact high-value contributions have the greater chance of having a meaningful impact on the Stellar network.
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR updates CONTRIBUTING.md to steer community contributions toward discussions, proposals, and well-scoped issues, and to narrow when pull requests are accepted across Stellar-hosted projects.
Changes:
Reframes contribution guidance toward discussions/ideas/experience reports and structured bug reports.
Adds new “Reporting Bugs and Requesting Features” and “Pull Requests” sections with stricter PR acceptance criteria.
Updates the “Getting Started” section with direct links to org discussions and protocol proposals.
Suppressed comments (1)
CONTRIBUTING.md:44
The doc uses American English ("behavior"), but this paragraph uses "behaviour". Please standardize spelling (e.g., change to "behavior").
other projects. Correctness is critical and thoughtful evolution of behaviour and APIs is paramount.
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
Suppressed comments (5)
Previously missed (2) — in code that hasn't changed since the last review.
CONTRIBUTING.md:26
These bullets include raw URLs even though the rest of the document uses Markdown links. Converting them improves readability and makes the link text clearer in rendered docs. CONTRIBUTING.md:42
This file still defines a [help-wanted] reference link; using it here makes the label actionable in the rendered doc and avoids an unused reference definition.
CONTRIBUTING.md:11
Spelling is inconsistent with the rest of this repo’s documentation (e.g., profile README uses “decentralized”). Using US spelling here will keep CONTRIBUTING.md consistent.
> The Stellar network is open, decentralised, and programmable. For many ideas you may have, they can
CONTRIBUTING.md:46
This paragraph mixes US and UK spelling (“behavior” vs “behaviour”) within the same document. Please standardize to match the repo’s prevailing usage (CODE_OF_CONDUCT.md uses “behavior”).
other projects. Correctness is critical and thoughtful evolution of behaviour and APIs is paramount.
CONTRIBUTING.md:54
The first bullet is grammatically awkward, and the document still defines a [commit-msg] reference link that is otherwise unused. Rewording the bullet and adding a commit-message bullet improves clarity and reuses the existing reference.
Key things to keep in mind when creating a pull request:
* Confirm, does the pull request narrowly address an open issue and have you been assigned?
* Fork the project's repository and submit the pull request from a branch in your fork.
* Link the approved issue and keep the pull request narrowly within the scope of that issue.
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
Suppressed comments (4)
Previously missed (3) — in code that hasn't changed since the last review.
CONTRIBUTING.md:42
The document defines a [help-wanted] reference link at the bottom; using it here avoids dead link definitions and makes the label reference clickable. CONTRIBUTING.md:46
Use US English spelling to match the rest of the repository documentation: “behaviour” should be “behavior”. CONTRIBUTING.md:54
This bullet is grammatically awkward (“Confirm, does…”). Rewording improves clarity; also consider referencing the existing [commit-msg] link so it isn’t left unused.
CONTRIBUTING.md:11
Use US English spelling to match the rest of the repository documentation (e.g., profile/README.md uses “decentralized”): “decentralised” should be “decentralized”.
> The Stellar network is open, decentralized, and programmable. For many ideas you may have, they can
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
Suppressed comments (2)
Previously missed (2) — in code that hasn't changed since the last review.
CONTRIBUTING.md:46
Use US English spelling (“behavior”) to match the repo’s documentation convention, and fix the grammar “dependencies to” → “dependencies of”. CONTRIBUTING.md:52
This bullet reads like a question with awkward punctuation (“Confirm, does…”). Rephrase to a direct checklist item for clarity.
Use the repository’s established US English spelling (behavior), which also appears earlier in this file at line 40 and throughout CODE_OF_CONDUCT.md (for example, line 47).
This no longer links contributors to the qualifying issues even though the existing [help-wanted] reference remains defined at line 110. Restoring the link makes the policy actionable and avoids leaving that reference unused.
Use US spelling behavior
CONTRIBUTING.md:55
Use the repository’s established US English spelling “behavior,” consistent with line 40 and CODE_OF_CONDUCT.md:47.
Formatting help wanted as code removes the link to the organization-wide issue queue, even though the [help-wanted] reference remains defined at CONTRIBUTING.md:103. Restore the link so contributors can find eligible issues.
Use established US English spelling
CONTRIBUTING.md:55
Use the repository's established US English spelling, which is also used earlier in this document (behavior on line 40).
Fix question grammar and punctuation
CONTRIBUTING.md:64
The first question incorrectly coordinates two different subjects under “Does,” and the second question ends with a period. Separate the clauses grammatically and use question marks consistently.
The retained [help-wanted] definition at line 115 is no longer referenced, so contributors cannot follow this guideline directly to find eligible issues. Keep the label linked as it was in the previous text.
Use US English spelling: behavior
CONTRIBUTING.md:55
Use the repository's established US English spelling, behavior, as seen in CODE_OF_CONDUCT.md:47 and CODE_OF_CONDUCT.md:55.
Clarify and unify the contribution eligibility requirements
CONTRIBUTING.md:48
This eligibility rule conflicts with the checklist below: here a help wanted label is sufficient, while lines 63 and 65 additionally require assignment and an “approved” issue, neither of which has a described process. State one consistent gate and explain how contributors obtain it; otherwise contributors cannot determine whether a pull request will be accepted.
Use consistent US English spelling: “behavior”
CONTRIBUTING.md:55
Use the repository’s established US English spelling, “behavior,” which is also used earlier in this document at line 40 and throughout CODE_OF_CONDUCT.md (for example, line 47).
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
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.
What
Revising the contribution guidelines to encourage high-impact high-value contributions, which we find are typically creating issues, participating in issues and discussions.
Why
High-impact high-value contributions have the greater chance of having a meaningful impact on the Stellar network.