Skip to content

Updateing Spec-Kit for a project using CLI with Here and Force should not overwrite Constitutuion #557

@PeteHalsted

Description

@PeteHalsted

I saw a few other topics that mention this in discussion about how to update, but wanted to make sure it this bubbles up as a feature request or in my opinion a bug. Using the CLI to update Spec-Kit in an existing project that already has Spec-Kit in it. Should overwrite the commands, scripts etc. but it should leave the constitution alone. Once the constitution is established, it should remain.

Folks have work arounds to save and replace it but that should be needed, it should either no be replaced by default or at the very least be a command line parameters to prevent it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions