and as the linked news is 20 hours old it is definitely fresh news that people want and should know about, despite the fact it has been fixed since then. the fix doesn’t mean it didn’t happen.
They specifically asked not to comment on the PR, comments on the PR don’t give the issue any extra visibility. They didn’t ask not to comment here or to stop making threads, they linked a PR and then asked not dogpile that specific PR.
That’s seems potentially likely. I can imagine maybe the programmer had a written at some point that the AI itself needed to state it was written by copilot whenever it made merges. Then when it worked on that area, that directive got skewed and ended up applying it to VS Code itself.
There is a difference between the justified public backlash that happened and the piling on the developer who merged the request after it was fixed.
there is and this is the former.
and as the linked news is 20 hours old it is definitely fresh news that people want and should know about, despite the fact it has been fixed since then. the fix doesn’t mean it didn’t happen.
They specifically asked not to comment on the PR, comments on the PR don’t give the issue any extra visibility. They didn’t ask not to comment here or to stop making threads, they linked a PR and then asked not dogpile that specific PR.
oh! well now it makes sense. i misread that part.
was the buggy commit done… because of AI?
That’s seems potentially likely. I can imagine maybe the programmer had a written at some point that the AI itself needed to state it was written by copilot whenever it made merges. Then when it worked on that area, that directive got skewed and ended up applying it to VS Code itself.