Replies: 2 comments
-
|
Just to answer my own question. If you are working a fork of someones project and still want to use OpenSpec, you can do the following: edit Naturally this also works for your Full power in your forks without bothering others with your garbage. |
Beta Was this translation helpful? Give feedback.
-
|
Another method would be to place a This works on the principle that git does not track empty directories and this file inside openspec/ tells git to ignore all files inside openspec/. I stole this idea from Jujutsu, how they hide their |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm trying to solve the idea I have for using OpenSpec in projects which will not allow the OpenSpec integration. Maybe having a global OpenSpec dir with spec from all foreign projects I'm working on. Of course OpenSpec should check for the existance if this project and automatically use this location for reading and storing artifacts. You don't want leave any openspec file left behind in the fereign project dir as you might accidentally commit this with git.
Anyone thinking about this case?
Beta Was this translation helpful? Give feedback.
All reactions