I'm not certain when this started happening. I stepped away for about a year, and now things have new names too 😆
Qodo keeps generating a .qodo directory as well. I'm not certain what it is currently meant for since it's empty. It seems like if it's meant for settings that the .vscode workspace settings could be utilized for that.
Over the years I've learned that your personal environment choices should not leak into your project and team, unless you've decided to be unified on something like version management tooling, IDE, etc. To me this feels like it should live in the global git ignore so that my team doesn't need to experience choices I've made on my machine.
I know it's a simple problem, but it can be annoying to open up an old project and next thing you know you've got uncommitted changes because of this.
Sometimes it gets me to the point of wanting to disable the extension, but I'd rather keep it.
I'm not certain when this started happening. I stepped away for about a year, and now things have new names too 😆
Qodo keeps generating a
.qododirectory as well. I'm not certain what it is currently meant for since it's empty. It seems like if it's meant for settings that the.vscodeworkspace settings could be utilized for that.Over the years I've learned that your personal environment choices should not leak into your project and team, unless you've decided to be unified on something like version management tooling, IDE, etc. To me this feels like it should live in the global git ignore so that my team doesn't need to experience choices I've made on my machine.
I know it's a simple problem, but it can be annoying to open up an old project and next thing you know you've got uncommitted changes because of this.
Sometimes it gets me to the point of wanting to disable the extension, but I'd rather keep it.