308
VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage (news.ycombinator.com)
submitted 6 months ago by to c/technology@lemmy.world
42 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 48 points 6 months ago (18 children)

This has been fixed. It was a bug, see this merge request: https://github.com/microsoft/vscode/pull/313931

There a quite a lot of toxic comments there already, please dont add to the pile.

  • permalink
  • fedilink
  • source
  • hideshow 18 child comments
    •
  • [–] 88 points 6 months ago (6 children)

    please dont add to the pile

    please do. it is first time i am hearing about this, for example. and i have my doubts this "bug" would have been fixed if it were not for a "lot of toxic comments"

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 18 points 6 months ago (5 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 26 points 6 months ago (2 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 10 points 6 months ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 6 months ago (1 child)

    was the buggy commit done… because of AI?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 5 points 6 months ago

    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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 37 points 6 months ago (7 children)

    The bug was fixed, but it still adds itself as co-author by default if you as much as use code completion powered by Copilot.

    Combined with the fact that this doesn't show up in your commit message dialog, and that is nothing but blatant advertising, this is just unacceptable.

    I don't necessarily mind crediting Copilot if it did substantial amount of the work, but it also seems redundant nowadays when AI has become as ubiquitous as using an IDE. Having used it for code completion just doesn't seem to warrant co-author credit in that context. In other words if I had been able to edit that part of the commit message I'd probably be a lot less annoyed by this.

    As it is, it's just blatant overreach by Microsoft. Microsoft doing Microsoft things. Nothing has changed since the 90s.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 13 points 6 months ago (3 children)

    Yeah, I don't include the person down the hall when I ask for their help unless they are making final design decisions alongside me. If copilot is doing 40% of the work, sure. Just existing nearby isn't enough.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 16 points 6 months ago (2 children)

    Also, CoPilot isn't a person. It shouldn't be a co-author for the same reason Google and StackOverflow aren't.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 10 points 6 months ago

    If I copy a solution from SO I usually put in a comment with a link to the answer to cite my source. I don't mind crediting where credit is due, but claiming co-author for a spelling correction is a bit much.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 4 points 6 months ago (1 child)

    If VSCode is just hijacking the in-IDE commit UI, is bypassing it as simple as committing from the command line?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 4 points 6 months ago

    Yes, you can get around it that way. You can also just disable it in VSCode settings. I could also just not use VSCode or CoPilot at all. It's not that can't be worked around; it's that we shouldn't have to. It's the violation of trust we're having issues with.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 4 points 6 months ago (1 child)

    The people in that thread who complain and threaten that they are Seriously Considering not trusting Microsoft any more unless they shape up immediately very soon...

    If they had any threshold for when they would pass judgement or take any action to switch to alternatives, it would have been passed long ago.

    They are just whining until they get distracted and forget about it. They will make the exact same noises the next time something like this happens. And the next, and the next...

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •