refactor: replace push-based sync with pull-based reusable workflow - #4
Merged
NWarila merged 1 commit intoApr 8, 2026
Merged
Conversation
Copy link
Copy Markdown
Owner
Sorry, something went wrong.
Remove sync-downstream.yml and its PAT requirement. Sync is now pull-based: each downstream repo calls self-update.yml as a reusable workflow via uses: nwarila/python-template/.github/workflows/self-update.yml@v1. - Extract inline sync logic into scripts/sync.py (standalone, testable) - Add workflow_call trigger to self-update.yml for downstream callers - Remove downstream_repos from sync-manifest.json (template doesn't push) - Add sync.py to manifest so downstream repos receive it - Document manifest-driven sync rationale vs submodules/packages - Update PLAN.md and README.md to reflect pull-based architecture
4 tasks
NWarila
added a commit
that referenced
this pull request
Jun 2, 2026
## Summary - **SECURITY.md**: Adds supported-version policy (latest release / `v1` tag), private vulnerability reporting via the GitHub Security tab, response-timeline table, and in/out-of-scope classification (scripts, workflows, reference configs; excludes upstream third-party tools). - **docs/decision-records/0001**: Captures the already-shipped decision that QA scripts are standalone and stdlib-only — no shared helper module, no third-party imports. Converts reasoning from PLAN.md Resolved Decision 14. - **docs/decision-records/0002**: Captures the already-shipped decision to use pull-based, manifest-driven template sync instead of push-based cross-repo credentials or git submodules. Converts reasoning from PLAN.md Resolved Decision 22 and the PR #4 refactor. - **docs/diagrams/qa-template-sync-flow.mmd**: Mermaid flowchart of the QA and template-sync flow — from `scripts/` through `auto-release.yml` → release tag → `self-update.yml` → downstream sync PR → `python-qa.yml` reusable workflow. - **README.md**: Adds a Security Policy badge alongside the existing CI, Coverage, Python, Platform, and License badges. - **.gitignore**: Adds allowlist entries for `SECURITY.md` and the new `docs/` directory tree (deny-all model requires explicit allowlisting of every new path). ## Test plan - [ ] markdownlint passes on all new and modified `.md` files (verified locally: 0 errors) - [ ] All new files appear as tracked in `git status --short` (verified: no files ignored) - [ ] No AI bylines, Co-authored-by trailers, or "generated by" text in files or commit message (verified via grep) - [ ] CI (`template-ci.yml`) passes on the PR
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Design
Each repo owns its own updates. The template publishes releases, consumers pull when ready. No cross-repo credentials, no push permissions, no coupling.
Downstream repos only need a thin wrapper:
Test plan