When the worst case is to lose your job and never deal with the legacy code again.
When the worst case is to lose your job and never deal with the legacy code again.
There’s automation and you can do it manually if needed. For example I have a couple of emulators that pull every 24 hours from GitHub just in case nint tendo gets a little lawsuit heavy. I also have one offs from GitHub that pull down when I want.
You can also mirror a public repo from GitHub into a private repo so it does not gets indexed/ai trained.
I had the same issue. I had to turn off AI features and it started working again. Specifically it stopped working on a peice of legacy code that had hundreds of thousands of lines of code all in one file. No idea what version of vscode but it was fairly recent.
I have a poster of that. So good.
Thank you for this.