FreeBSD/src
1
0
Fork 0
mirror of https://git.FreeBSD.org/src.git synced 2026-06-02 11:24:32 +00:00
Code Issues Projects Releases Wiki Activity

CONTRIBUTING: fix typos in GitHub contribution guide

Browse Source 
Signed-off-by: Roman <nnov.brody@gmail.com>
Pull-request: https://github.com/freebsd/freebsd-src/pull/2156
This commit is contained in:
Roman
2026-04-21 22:16:15 +03:00
committed by Ed Maste
parent 69e8d8b49d
commit b6dd9d3593
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CONTRIBUTING.md
+4 -4
View File
@@ -21,7 +21,7 @@ changes where the contributor already has a GitHub account.
A change should be submitted by only one method. For example, please do not A change should be submitted by only one method. For example, please do not
open a GitHub pull request and create a Phabricator review for the same change open a GitHub pull request and create a Phabricator review for the same change
(unless explicitly requested to do so by a FreeBSD committer). If asked to move (unless explicitly requested to do so by a FreeBSD committer). If asked to move
from Github to Phabricator, please close the Github pull request adding the URL from GitHub to Phabricator, please close the GitHub pull request adding the URL
of the Phabricator review as a comment. of the Phabricator review as a comment.
## GitHub Pull Requests ## GitHub Pull Requests
@@ -76,7 +76,7 @@ Before submitting, ensure:
* Each commit is suitable for direct inclusion in the FreeBSD's repository. * Each commit is suitable for direct inclusion in the FreeBSD's repository.
* Pull Request scope must remain stable during review. If feedback expands * Pull Request scope must remain stable during review. If feedback expands
scope, create a new Pull Request. scope, create a new Pull Request.
* Rebase your chages (and update with a forced push) when incorporating review * Rebase your changes (and update with a forced push) when incorporating review
feedback, rather than using a merge commit. feedback, rather than using a merge commit.
#### Commit Messages #### Commit Messages
@@ -84,7 +84,7 @@ Before submitting, ensure:
Each commit must: Each commit must:
* Follow the [commit log message guide](https://docs.freebsd.org/en/articles/committers-guide/#commit-log-message). * Follow the [commit log message guide](https://docs.freebsd.org/en/articles/committers-guide/#commit-log-message).
* Include one ore more `Signed-off-by:` trailers certifying [Developer Certificate of Origin](https://developercertificate.org/). * Include one or more `Signed-off-by:` trailers certifying [Developer Certificate of Origin](https://developercertificate.org/).
* Include `PR: \<bugnumber\>` if fixing a Bugzilla Problem Report. * Include `PR: \<bugnumber\>` if fixing a Bugzilla Problem Report.
* Include the URL of a related code review, if applicable. * Include the URL of a related code review, if applicable.
(Avoid opening both Phabricator/Differential reviews and GitHub Pull Requests (Avoid opening both Phabricator/Differential reviews and GitHub Pull Requests
@@ -103,7 +103,7 @@ Each commit must:
### Additional Requirements for FreeBSD Committers ### Additional Requirements for FreeBSD Committers
* Committers submitting Pull Requests are for pushing their changes to the tree * Committers submitting Pull Requests are responsible for pushing their changes to the tree
(including obtaining any required approvals). (including obtaining any required approvals).
* Pull Requests opened by FreeBSD committers may be closed after one month * Pull Requests opened by FreeBSD committers may be closed after one month
unless there is a strong reason to keep them open. unless there is a strong reason to keep them open.