Add configurable git branch templates for monorepos#3293
Draft
PascalThuet wants to merge 1 commit into
Draft
Conversation
Assisted-by: Codex (model: GPT-5, autonomous)
Collaborator
|
I realize this still a draft, but I wanted to make sure that you should merge the template into the git-config.yml for ease of use |
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
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
branch_templateconfig with{author},{app},{number}, and{slug}tokens, plusbranch_prefixas a shorthand namespace.{number}-{slug}behavior unchanged.Why
Monorepo installs can have separate Spec Kit projects but one shared root Git branch namespace. This lets projects opt into names like
jdoe/app-a/008-guided-tourwithout requiring separate Git repositories or changing downstream feature path resolution.Fixes #3081.
Implementation note
This follows the concrete use case and change-surface analysis in #3081 (comment). That comment is relevant because it identifies the desired
{author}/{app}/{number}-{slug}shape and notes that downstream commands already resolve feature directories through.specify/feature.json/SPECIFY_FEATURE_DIRECTORY, so branch creation and validation are the main places that need to become namespace-aware.Validation
.venv/bin/python -m pytest tests/extensions/git/test_git_extension.py tests/test_timestamp_branches.py -qDisclosure
Prepared on behalf of @PascalThuet by Codex (model: GPT-5, autonomous). The commit includes an
Assisted-by:trailer.