CONTRIBUTING: Add a note discouraging unneccessary CI runs due to the "Update branch" feature being used too often (project-chip#38009)

* CONTRIBUTING: Add a note discouraging unneccessary CI runs due to the "Update branch" feature being used too often

Signed-off-by: Maciej Grela <m.grela@samsung.com>

* Restyled by prettier-markdown

* Update CONTRIBUTING.md

Restore proper tip formatting according to GitHub Markdown manual.

Co-authored-by: Arkadiusz Bokowy <arkadiusz.bokowy@gmail.com>

* Update CONTRIBUTING.md

* restyled: restyled release now ships restyler-linux-x86_64 properly now

Signed-off-by: Maciej Grela <m.grela@samsung.com>

* Restyled by prettier-markdown

---------

Signed-off-by: Maciej Grela <m.grela@samsung.com>
Co-authored-by: Restyled.io <commits@restyled.io>
Co-authored-by: Arkadiusz Bokowy <arkadiusz.bokowy@gmail.com>

Author: 3 people

.github/workflows/restyled.yml

@@ -15,11 +15,6 @@ jobs:
         uses: actions/checkout@v4
 
       - uses: restyled-io/actions/setup@v4
-        with:
-          # TODO: Pinned to v0.6.0.2 because the latest release does not have a pre-built
-          # 'restyler-linux' asset. This broke our workflow as we rely on the pre-built binary.
-          # Remove this pin once a new release with the 'restyler-linux' asset is available.          
-          tag: 'v0.6.0.2'
 
       - id: restyler
         uses: restyled-io/actions/run@v4

CONTRIBUTING.md

@@ -253,6 +253,15 @@ out of convenience.
     fixing a typo in an ID still requires some description on how you checked
     that the new ID takes effect.
 
+> [!TIP]
+>
+> When working on a pull request for Matter SDK refrain from using the "Update
+> branch" feature in the GitHub UI too often. Updating the PR branch in this way
+> triggers the CI workflows cancellation and restart. This feature should be
+> used only when a PR has not been worked on for a long time and a lot of
+> divergence has accumulated. Your PR branch being out of sync with master is
+> not a blocker for merging an approved PR.
+
 ### Review Requirements
 
 #### Documentation Best Practices