Skip to content

[CONTRIBUTING.md] Clarify that PRs should originate from your own fork #10009

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 28, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,10 +49,11 @@ In general, you should not directly commit changes to a draft unless you are an
Editor of that draft, or have their explicit permission. If you are not an
Editor of a draft, but wish to contribute changes, the best practice is to either
work directly with an Editor to review proposed text, or file your proposal as a
pull request (PR). Substantive changes need WG consensus, not merely Editor
agreement; typographic error and markup fixes are generally okay to commit, but
any substantive changes should have clear WG consensus. Substantial changes or
additions to non-normative text should still have clear Editor approval.
pull request (PR) originating from your own fork. Substantive changes
need WG consensus, not merely Editor agreement; typographic error and markup fixes
are generally okay to commit, but any substantive changes should have
clear WG consensus. Substantial changes or additions to non-normative text
should still have clear Editor approval.

In any case, WG consensus is expected prior to merging changes, and consensus is
determined by the Chairs (not self-assessed) via synchronous decisions during
Expand Down