just ignore， only internal use for reivew code .

.github/.wordlist.txt

@@ -1719,3 +1719,13 @@ Zigbee
 zigbeealliance
 zigbeethread
 zsdk
+bdk
+Changelog
+changelog
+devicetree
+DLM
+downloaders
+ILM
+tlk
+TLX
+udev

.github/workflows/chef.yaml

@@ -31,6 +31,7 @@ env:
 
 jobs:
     chef_linux_all_devices:
+        if:false
         name: Chef - Linux CI Examples (All chef devices)
         timeout-minutes: 120
         runs-on: ubuntu-latest
@@ -55,6 +56,7 @@ jobs:
                   ./scripts/run_in_build_env.sh "./examples/chef/chef.py --ci_linux"
 
     chef_device_functional_test:
+        if:false
         name: Chef - Device functional tests (Linux)
         if: github.actor != 'restyled-io[bot]'
         timeout-minutes: 90
@@ -93,6 +95,7 @@ jobs:
                   scripts/run_in_python_env.sh out/python_env './scripts/tests/run_python_test.py --app examples/chef/linux/out/rootnode_dimmablelight_bCwGYSDpoe --factory-reset --script ./examples/chef/tests/dimmablelight_test.py --script-args "--commissioning-method on-network --discriminator 3840 --passcode 20202021" --app-stdin-pipe /tmp/chef_stdin.txt'
 
     chef_esp32:
+        if:false
         name: Chef - ESP32 CI Examples
         runs-on: ubuntu-latest
         if: github.actor != 'restyled-io[bot]'
@@ -145,7 +148,7 @@ jobs:
         if: github.actor != 'restyled-io[bot]'
 
         container:
-            image: ghcr.io/project-chip/chip-build-telink:181
+            image: ghcr.io/project-chip/chip-build-telink:185
             volumes:
                 - "/:/runner-root-volume"
             options: --user root

.github/workflows/examples-esp32.yaml → .github/workflows/examples-esp32.yaml.disabled

@@ -181,6 +181,7 @@ jobs:
                 platform-name: ESP32
 
     esp32_1:
+        if:false
         name: ESP32_1
 
         runs-on: ubuntu-latest

.gitignore

@@ -96,3 +96,9 @@ imgui.ini
 
 # Joint Fabric test harness output file
 admin_storage.json
+
+# ignore build output directories
+build-*
+build_*
+factory_data*
+*.patch

.mergify.yml

@@ -1,42 +1,232 @@
 pull_request_rules:
-  - name: Label conflicting pull requests
-    description: Add a label to a pull request with conflict to spot it easily
-    conditions:
-      - conflict
-      - '-closed'
-    actions:
-      label:
-        toggle:
+    - name: Label conflicting pull requests
+      description: Add a label to a pull request with conflict to spot it easily
+      conditions:
           - conflict
-  # WARNING: If the rule name below is changed, you must also update the
-  # condition `check-failure~=Automatic merge on PullApprove` to match the new name.
-  - name: Automatic merge on PullApprove
-    conditions:
-      - or:
-          - check-success=pullapprove
-          - label="fast track"
-      - '#approved-reviews-by>=1'
-      - '#review-threads-unresolved=0'
-      - '-draft'
-      - label!=docker
-      # Workaround for Mergify deadlock due to using "#check-failure=0":
-      # Mergify’s own action check can appear as failed/cancelled if conditions stop matching;
-      # and GitHub keeps those historic failures forever. Since `#check-failure=0` counts ALL
-      # failures (including historic ones), this would cause a deadlock and block merges indefinitely.
-      # We whitelist only this self-check so merges aren’t deadlocked, while all other failures still block.
-      - or:
-          - '#check-failure=0'
-          - and:
-              - '#check-failure=1'
-              # WARNING: This must match the rule name defined above.
-              # If the rule name changes, update this condition accordingly.
-              - check-failure~=Automatic merge on PullApprove
-      - '#check-pending=0'
-      - check-success~=Build
-      - or:
-          - check-success=pullapprove
-          - check-skipped=pullapprove
-          - check-neutral=pullapprove
-    actions:
-      merge:
-        method: squash
+          - "-closed"
+      actions:
+          label:
+              toggle:
+                  - conflict
+    # WARNING: If the rule name below is changed, you must also update the
+    # condition `check-failure~=Automatic merge on PullApprove` to match the new name.
+    - name: Automatic merge on PullApprove
+      conditions:
+          - or:
+                - check-success=pullapprove
+                - label="fast track"
+          - "#approved-reviews-by>=1"
+          - "#review-threads-unresolved=0"
+          - "-draft"
+          - label!=docker
+          # Workaround for Mergify deadlock due to using "#check-failure=0":
+          # Mergify's own action check can appear as failed/cancelled if conditions stop matching;
+          # and GitHub keeps those historic failures forever. Since `#check-failure=0` counts ALL
+          # failures (including historic ones), this would cause a deadlock and block merges indefinitely.
+          # We whitelist only this self-check so merges aren't deadlocked, while all other failures still block.
+          - or:
+                - "#check-failure=0"
+                - and:
+                      - "#check-failure=1"
+                      # WARNING: This must match the rule name defined above.
+                      # If the rule name changes, update this condition accordingly.
+                      - check-failure~=Automatic merge on PullApprove
+          - "#check-pending=0"
+          - check-success~=Build
+          - or:
+                - check-success=pullapprove
+                - check-skipped=pullapprove
+                - check-neutral=pullapprove
+      actions:
+          merge:
+              method: squash
+
+    # Backport rules - cherry-pick the squashed master commit after merge.
+    # Apply a request-backport-* label (such as request-backport-latest or
+    # request-backport-supported) on the master PR (before or after merge)
+    # to trigger the corresponding backport.
+    - name: Backport to v1.7-branch
+      conditions:
+          - merged
+          - base=master
+          - or:
+                - label="request-backport-latest-mve-sve"
+                - label="request-backport-latest"
+                - label="request-backport-supported"
+      actions:
+          backport:
+              branches:
+                  - v1.7-branch
+              labels:
+                  - backport-v1.7-branch
+
+    - name: Backport to v1.6.1-branch
+      conditions:
+          - merged
+          - base=master
+          - or:
+                - label="request-backport-latest-mve-sve"
+                - label="request-backport-supported"
+      actions:
+          backport:
+              branches:
+                  - v1.6.1-branch
+              labels:
+                  - backport-v1.6.1-branch
+
+    - name: Backport to v1.6.1-mve-branch
+      conditions:
+          - merged
+          - base=master
+          - label="request-backport-latest-mve-sve"
+      actions:
+          backport:
+              branches:
+                  - v1.6.1-mve-branch
+              labels:
+                  - backport-v1.6.1-mve-branch
+
+    - name: Backport to v1.6-branch
+      conditions:
+          - merged
+          - base=master
+          - label="request-backport-supported"
+      actions:
+          backport:
+              branches:
+                  - v1.6-branch
+              labels:
+                  - backport-v1.6-branch
+
+    - name: Backport to v1.4.2-branch
+      conditions:
+          - merged
+          - base=master
+          - label="request-backport-supported"
+      actions:
+          backport:
+              branches:
+                  - v1.4.2-branch
+              labels:
+                  - backport-v1.4.2-branch
+
+    # Telink fork backport rules - cherry-pick the squashed dev/master commit.
+    # Apply a request-backport-<branch> label on a dev-tlk_v* / master PR.
+    - name: Backport to release-v1.0-v1.5-branch
+      conditions:
+          - merged
+          - or:
+                - base=master
+                - base~=^dev-tlk_
+          - label="request-backport-release-v1.0-v1.5-branch"
+      actions:
+          backport:
+              branches:
+                  - release-v1.0-v1.5-branch
+              labels:
+                  - backport-release-v1.0-v1.5-branch
+
+    - name: Backport to pre_release-v1.1-v1.5-branch
+      conditions:
+          - merged
+          - or:
+                - base=master
+                - base~=^dev-tlk_
+          - label="request-backport-pre_release-v1.1-v1.5-branch"
+      actions:
+          backport:
+              branches:
+                  - pre_release-v1.1-v1.5-branch
+              labels:
+                  - backport-pre_release-v1.1-v1.5-branch
+
+    - name: Backport to pre_release-v1.2-v1.5-branch
+      conditions:
+          - merged
+          - or:
+                - base=master
+                - base~=^dev-tlk_
+          - label="request-backport-pre_release-v1.2-v1.5-branch"
+      actions:
+          backport:
+              branches:
+                  - pre_release-v1.2-v1.5-branch
+              labels:
+                  - backport-pre_release-v1.2-v1.5-branch
+
+    - name: Backport to pre_release-v1.1-v1.6.1-branch
+      conditions:
+          - merged
+          - or:
+                - base=master
+                - base~=^dev-tlk_
+          - label="request-backport-pre_release-v1.1-v1.6.1-branch"
+      actions:
+          backport:
+              branches:
+                  - pre_release-v1.1-v1.6.1-branch
+              labels:
+                  - backport-pre_release-v1.1-v1.6.1-branch
+
+    - name: Backport to v1.5-branch
+      conditions:
+          - merged
+          - or:
+                - base=master
+                - base~=^dev-tlk_
+          - label="request-backport-v1.5-branch"
+      actions:
+          backport:
+              branches:
+                  - v1.5-branch
+              labels:
+                  - backport-v1.5-branch
+
+    - name: Request review for MVE/SVE backports
+      conditions:
+          - author=mergify[bot]
+          - or:
+                - label~=mve-branch
+                - label~=sve-branch
+      actions:
+          request_reviews:
+              users:
+                  - cecille
+
+    # Auto-merge backport PRs when CI is green and there are no conflicts.
+    # If a cherry-pick has conflicts or CI fails, the PR is left open for manual resolution.
+    # WARNING: If the rule name below is changed, you must also update the
+    # condition `check-failure~=Auto-merge clean backport PRs` to match the new name.
+    - name: Auto-merge clean backport PRs
+      conditions:
+          - or:
+                - label="backport-v1.7-branch"
+                - label="backport-v1.6.1-branch"
+                - label="backport-v1.6-branch"
+                - label="backport-v1.5-branch"
+                - label="backport-v1.4.2-branch"
+                - label="backport-release-v1.0-v1.5-branch"
+                - label="backport-pre_release-v1.1-v1.5-branch"
+                - label="backport-pre_release-v1.2-v1.5-branch"
+                - label="backport-pre_release-v1.1-v1.6.1-branch"
+          - author=mergify[bot]
+          - "-conflict"
+          - "-draft"
+          # Same deadlock workaround as above: allow exactly 1 failure if it is
+          # this rule's own self-check (which Mergify marks failed when conditions
+          # stop matching, and GitHub retains that historic failure forever).
+          - or:
+                - "#check-failure=0"
+                - and:
+                      - "#check-failure=1"
+                      # WARNING: This must match the rule name defined above.
+                      # If the rule name changes, update this condition accordingly.
+                      - check-failure~=Auto-merge clean backport PRs
+          - "#check-pending=0"
+          - check-success~=Build
+      actions:
+          merge:
+              method: squash
+
+merge_protections_settings:
+    reporting_method: check-runs