Updated Contributor Policies (markdown)

Joshua M. Boniface 2019-01-01 19:54:56 -05:00
parent a6ded00401
commit f70d10c01d

@ -2,7 +2,7 @@ This page describes general procedures for the contributors with write access to
1. Contributors should set code ownership `CODEOWNERS` files wherever they consider themselves subject-matter expects, to assist in the review process. 1. Contributors should set code ownership `CODEOWNERS` files wherever they consider themselves subject-matter expects, to assist in the review process.
1. PRs to `dev` should have at least one review by a code owner before being merged. More reviews are always better, especially for large PRs. 1. PRs to `dev` should have at least one review by a code owner before being merged. If a section does not have a codeowner, any contributor may review it. More reviews are always better, especially for large PRs or if there are no defined codeowners.
1. PRs to `dev` should be merged as "Rebase and merge" to avoid a cluttered history. 1. PRs to `dev` should be merged as "Rebase and merge" to avoid a cluttered history.