Add git-based template synchronization for downstream projects #102
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.


Downstream projects need to receive template updates (especially dependabot-driven dependency updates) while preserving their git history and project-specific modifications.
Implementation
Core Sync Mechanism (
tools/template-sync.py)Configuration (
.templaterc)Documentation
docs/template-sync.md- Setup, workflow, configuration referencedocs/template-sync-examples.md- 10 real-world scenarios (conflict resolution, selective sync, emergency updates)docs/template-sync-quickstart.md- Command referenceOptional Automation (
.github/workflows/template-sync-check.yaml.example)Usage
Design Rationale
Git merge handles dependency updates naturally—when template's
pyproject.tomlupdates pytest 8.2→8.3 via dependabot, downstream projects receive it as a merge commit. Standard 3-way merge preserves both template updates and local modifications. No external dependencies beyond Python stdlib + Git.💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.