aboutsummaryrefslogtreecommitdiff
path: root/website
diff options
context:
space:
mode:
authorWarner Losh <imp@FreeBSD.org>2026-07-14 22:59:44 +0000
committerWarner Losh <imp@FreeBSD.org>2026-07-14 22:59:44 +0000
commit5055f6624bd0bdf00c4a94cfd7cccb9b31a3b9c6 (patch)
treefbbcead90b4f4d48a73307b6383a883d382be11f /website
parent6c3661df1e104877e4571b5af6afed8f133b4153 (diff)
Diffstat (limited to 'website')
-rw-r--r--website/content/en/internal/cross-repo-commits.adoc3
1 files changed, 3 insertions, 0 deletions
diff --git a/website/content/en/internal/cross-repo-commits.adoc b/website/content/en/internal/cross-repo-commits.adoc
index bb8019479e..1b567f2e8d 100644
--- a/website/content/en/internal/cross-repo-commits.adoc
+++ b/website/content/en/internal/cross-repo-commits.adoc
@@ -16,6 +16,9 @@ This policy provides flexibility for contributors to commit across repositories
** *Expert Consultation:* Repository experts are consulted for non-trivial changes.
** *Stricter Rules:* The committer remains deferential to areas requiring formal oversight (e.g., the `ports/Mk` tree).
** *Scale:* The larger or more complex the change, the more critical it is to seek review and wait for explicit approval.
+** *When in Doubt:* Seek review from a committer experienced in the target repository before committing.
* *Accountability:* Committers must accept feedback on both process and content. If a mistake occurs, the default action is an immediate backout, followed by a more formal review, as appropriate.
When in doubt, ask first and seek a sanity check.
+
+See the extref:{committers-guide}[Committer's Guide] for specific blanket grants and commit message conventions.