[chore] Move v1 cookiecutter templates #109
Merged
Conversation
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
Contributor
Author
This was referenced Oct 28, 2025
sfc-gh-bnisco
force-pushed
the
v2-support-scaffold
branch
3 times, most recently
from
fef7ca4 to
6cfda26
Compare
kmcgrady
approved these changes
Oct 29, 2025
sfc-gh-bnisco
force-pushed
the
v2-support-scaffold
branch
from
6cfda26 to
6f4a420
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
TL;DR
Reorganized the component template structure to support versioning and updated the README with uvx usage instructions.
What changed?
v1subdirectory to support versioninguvxdev.pywith consistent stylingv1directoryWhy make this change?
This change prepares the component template for future versioning by organizing the cookiecutter templates into a versioned directory structure.