Skip to content

feat(init): add --force to render over an existing spectre directory - #60

Merged
jvmakine merged 1 commit into
mainfrom
juho/init-force
Oct 23, 2026
Merged

jvmakine merged 1 commit into
mainfrom
juho/init-force

Conversation

@jvmakine

Copy link
Copy Markdown
Collaborator

spectre init refuses a checkout that already has a spectre/ directory. Picking up template changes meant deleting it first, which also lost files the template doesn't write, such as descriptors and scripts added during the migration.

--force (-f) skips that check. scaffolder already overwrites in place: every file the template writes is replaced, symlinks are recreated, and other files are left alone. Template files the service has changed since, such as state.toml, are overwritten too, so review the diff before committing.

🤖 Generated with Claude Code

Picking up template changes meant deleting spectre/ first, losing files the
template does not write, such as descriptors and scripts added during the
migration.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@jvmakine
jvmakine requested a review from alecthomas as a code owner October 23, 2026 01:58
@jvmakine
jvmakine merged commit d6c1dfe into main Oct 23, 2026
6 checks passed
@jvmakine
jvmakine deleted the juho/init-force branch October 23, 2026 02:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant