Distributed backend specialist. Perfectly happy playing second fiddle—it means I get to chase fun ideas, dodge meetings, and break things no one told me to touch, all without anyone questioning it. 😇
That's exactly what the Co-authored-by line is—it's been there for as long as I can remember. I just re-purposed it and added similar ones for different "categories" of contribution.
Also, you could theoretically set up auto-commits with some VS Code settings and really good instructions. Copilot custom agents (formerly chat modes) could be handy for this, too.
Copilot coding agent accounts for the commits you're referencing, today. 😀 I show up as a co-author because it worked based on my prompt or comments for each step except the first where it's instructions came directly from GitHub.
Co-authored-by is a nice workaround, but it's not really filling the gap entirely. It'd be a lot more convenient if git properly supported multiple authors rather than expecting tools to be aware of a loose convention.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
That's exactly what the
Co-authored-byline is—it's been there for as long as I can remember. I just re-purposed it and added similar ones for different "categories" of contribution.Also, you could theoretically set up auto-commits with some VS Code settings and really good instructions. Copilot custom agents (formerly chat modes) could be handy for this, too.
Copilot coding agent accounts for the commits you're referencing, today. 😀 I show up as a co-author because it worked based on my prompt or comments for each step except the first where it's instructions came directly from GitHub.
Here's an example:
Co-authored-byis a nice workaround, but it's not really filling the gap entirely. It'd be a lot more convenient if git properly supported multiple authors rather than expecting tools to be aware of a loose convention.