docs: expand sync rule to require full pattern compliance check

When syncing local repos, verify all documented CI/CD patterns
are adopted — not just the one that triggered the sync.
This commit is contained in:
2026-03-25 23:15:54 +03:00
parent 43c84ae515
commit 807d73dfc3
+2
View File
@@ -7,3 +7,5 @@ When adding, removing, or renaming any file in this repository, **update README.
## MANDATORY: Keep local repos in sync with CI/CD docs
If `LocalRepos.md` exists, read it after updating any CI/CD-related documentation (e.g., `gitea-python-ci-cd.md`, `windows-code-signing.md`). For each listed repo, check whether the change applies to that project's CI workflows, build scripts, or installer configuration — and propagate relevant updates (e.g., NSIS patterns, VBS launchers, workflow fixes, troubleshooting notes) to the corresponding files in those repos.
When syncing, don't limit the check to just the pattern that changed — verify that each repo has adopted **all** documented patterns that apply to it (e.g., release notes from file, release fallback logic, VBS hidden launcher, Portainer webhook, size optimizations). Report any gaps found.