Replies: 2 comments 1 reply
|
One way to keep an installation of spec-kit updatable could be to have a normal Git checkout of spec-kit somewhere and symlink the relevant folders from another project. This way the developer could just go to spec-kit checkout and update it whenever they want. There may be some caveats with this approach, I haven't tried that. Also, it would prevent one from having project-local edits to spec-kit prompts and scripts (but that may be a niche use case). |
0 replies
|
When you have intit a project with like this |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I would like to have some command (for example /update), that will update the spec-kit usage in my project to a newer version (default newest, or I could specify it myself) and then the spec-kit would use new templates but will keep my settings (constitution, etc).
All reactions