To comply with GPL, it would have to automatically re-license your project as GPL too, right?

If you use GPL code, you may have to relicense your project.

Bard can share with you any code that it is licensed to distribute (which includes GPL).

But copilot actually outputs code into your project, do you really want citations there? I prefer to just enable the setting for it to not reproduce code verbatim from other projects.

Isn't it normal to copy code with citations into your project? It also helps document what's going on.

Sounds like a codebase filled with the ghosts of programmer past. Just put the code in and own maintaining it. Anyone can do a git blame and find the history of its implementation, and also see the original PR which should have described what it was doing, and provided far more context to the reviewers than a code comment.

And if an architecture decision is so significant, retain a repository of architecture decision records.

I think you misunderstood what I mean. I'm talking about:

    // Credit Foo Project per MIT license
    // See <https://github.com./foo/project/path/to/file

    fn some_foo_fn() {

This has nothing to do with git history.