When syncing local repos, verify all documented CI/CD patterns are adopted — not just the one that triggered the sync.
1.1 KiB
Project Instructions
MANDATORY: Keep README in sync
When adding, removing, or renaming any file in this repository, update README.md to reflect the change. The README serves as the index of all repository contents — every document must be listed there with a short description. Also update the "Last updated" date in README.md to the current date.
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.