From dd8d10a50a51a0c4d4f451fcc04125d2da20a8df Mon Sep 17 00:00:00 2001 From: Sergei Lissianoi Date: Fri, 22 Aug 2025 11:01:33 -0400 Subject: [PATCH 1/4] Mention the doccurator branches --- .github/CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index d0e9a88..cebf308 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -92,7 +92,7 @@ Please follow the official GitHub [guide](https://opensource.guide/how-to-contri When you created an issue and based on the discussion you want to contribute with your source-code. Branching is disabled on the public Silicon Labs repositories. You need to fork your own repo first. Please follow the official GitHub [guide](https://docs.github.com/en/get-started/exploring-projects-on-github/contributing-to-a-project). -You can create your branch on your own forked repo now. +You can create your branch on your own forked repo now. Pull requests must be merged into the doccurator branches corresponding to the Matter release the change applies to, for example `doccurator/2.6.2`. ### Branch Naming Convention Branch naming shall follow the following template: *IssueNumber-issue-title-goes-here* @@ -115,7 +115,7 @@ Another line of really good description ``` ## Pull Request Guideline -Okay you finished your work committed all your changes to your branch. Time to create a pull request. +Okay you finished your work committed all your changes to your branch. Time to create a pull request. Pull requests must be merged into the doccurator branches corresponding to the Matter release the change applies to, for example `doccurator/2.6.2`. Refer to the general pull request [guideline](https://opensource.guide/how-to-contribute/#opening-a-pull-request) from GitHub. What to consider when raising a Pull Request: 1. **Pull Request Naming** From 66d407eb3408ed919a3a88fe262746d6f2568221 Mon Sep 17 00:00:00 2001 From: Sergei Lissianoi Date: Fri, 22 Aug 2025 11:25:32 -0400 Subject: [PATCH 2/4] Mention the doccurator branches in the PR template --- .github/PULL_REQUEST_TEMPLATE.md | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index 62c2f6f..6e362a9 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -1,5 +1,6 @@ ## Description + ## Related Issue From 0e440ce9ad024b955e4df749e2fc5ffed6a44d11 Mon Sep 17 00:00:00 2001 From: silabs-vm Date: Tue, 16 Sep 2025 15:37:13 -0500 Subject: [PATCH 3/4] Update CONTRIBUTING.md Fixed typo --- .github/CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index cebf308..a673ec5 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -18,7 +18,7 @@ As a contributor, you'll want to be familiar with the Silicon Labs tooling: Read the Silicon Labs [coding guidelines](https://github.com/SiliconLabsSoftware/agreements-and-guidelines/blob/main/coding_standard.md). ## Git Setup -We need to know who you are, and how to contact you. Please ass the following information to your Git installation: +We need to know who you are, and how to contact you. Please add the following information to your Git installation: ``` git config --global user.name "FirstName LastName" git config --global user.email "firstname.lastname@example.com" @@ -115,7 +115,7 @@ Another line of really good description ``` ## Pull Request Guideline -Okay you finished your work committed all your changes to your branch. Time to create a pull request. Pull requests must be merged into the doccurator branches corresponding to the Matter release the change applies to, for example `doccurator/2.6.2`. +Okay you finished your work committed all your changes to your branch. Time to create a pull request. Pull requests must be merged into the doccurator branches corresponding to the Matter release the change applies to (for example, `doccurator/2.6.2`). Refer to the general pull request [guideline](https://opensource.guide/how-to-contribute/#opening-a-pull-request) from GitHub. What to consider when raising a Pull Request: 1. **Pull Request Naming** From 78f45b4e6afa22bcae5519d8fb1ac921942fa91f Mon Sep 17 00:00:00 2001 From: silabs-vm Date: Tue, 16 Sep 2025 15:38:58 -0500 Subject: [PATCH 4/4] Update CONTRIBUTING.md fixed typo --- .github/CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index a673ec5..2b27365 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -92,7 +92,7 @@ Please follow the official GitHub [guide](https://opensource.guide/how-to-contri When you created an issue and based on the discussion you want to contribute with your source-code. Branching is disabled on the public Silicon Labs repositories. You need to fork your own repo first. Please follow the official GitHub [guide](https://docs.github.com/en/get-started/exploring-projects-on-github/contributing-to-a-project). -You can create your branch on your own forked repo now. Pull requests must be merged into the doccurator branches corresponding to the Matter release the change applies to, for example `doccurator/2.6.2`. +You can create your branch on your own forked repo now. Pull requests must be merged into the doccurator branches corresponding to the Matter release the change applies to (for example, `doccurator/2.6.2`. ### Branch Naming Convention Branch naming shall follow the following template: *IssueNumber-issue-title-goes-here*