Move attribution to Copilot section

Author: woitaszek

docs/developer-experience/copilots.md

@@ -62,3 +62,44 @@ Chat AI tools are only as good as the prompts you give them. The quality and app
 
 If you make use of AI tools, it is important to understand how the data (including private or commercial code) might be used by the system. You can read more about how GitHub copilot handles your data and code at the [GitHub Copilot Privacy FAQ](https://github.com/features/copilot/#faq) and how to [manage Copilot policies](https://docs.github.com/en/copilot/how-tos/manage-your-account/manage-policies).
 
+## Attributing AI-Assisted Code Authorship
+
+When using AI tools to generate code, it can be beneficial to maintain transparency about authorship for accountability, code review, and auditing purposes. This can be done easily by using [Git trailers](https://git-scm.com/docs/git-interpret-trailers) that append structured metadata to the end of commit messages.
+
+### Agentic Code Authorship
+
+When using agentic AI tools to generate code, such as the GitHub Coding Agent feature where a GitHub issue (such as a story or task) can be assigned to a software engineering bot that analyzes the request, creates a branch, writes commits, and opens a pull request, authorship is typically attributed using tool-specific mechanisms that follow conventions similar to pair programming. For example, the GitHub Coding Agent creates its commits using the agent as an author with the supervising person acknowledged using the `Co-authored-by` trailer in the commit message. This allows AI-generated code to be attributed to the agent while still giving credit (and accountability) to the person who supervised or initiated the task.
+
+### IDE Assistant Attribution
+
+When using an AI coding assistant inside an IDE, such as the GitHub Copilot extension in Visual Studio Code, consider providing attribution in cases when the commit consists of primarily AI-generated code. This might occur when:
+
+* More than 50% of the lines in the commit were generated by AI
+* The AI provided the core logic or algorithmic approach
+* Substantial code blocks were accepted from AI suggestions
+
+This can be done by appending one or more custom trailers in the commit message, such as:
+
+```text
+Assistant-model: GPT-4o
+```
+
+Because most Git tooling expects `Co-authored-by` trailers to be formatted as email addresses, you should use a different trailer key to avoid confusion and to distinguish authorship from assistance.
+
+Trailers can be added manually at the end of a commit message, or by using the `git commit` command with the `--trailer` option:
+
+```sh
+git commit --message "Implement feature" --trailer "Assistant-model: GPT-4o"
+```
+
+Trailers can be displayed using the [pretty formats](https://git-scm.com/docs/pretty-formats#Documentation/pretty-formats.txt-trailersoptions) option to `git log` command. For example, for a formatted history showing the hash, author name, and assistant models used for each commit:
+```sh
+git log --color --pretty=format:"%C(yellow)%h%C(reset) %C(blue)%an%C(reset) [%C(magenta)%(trailers:key=Assistant-model,valueonly=true,separator=%x2C)%C(reset)] %s%C(bold cyan)%d%C(reset)"
+```
+```text
+2100e6c Author [GPT-4.1,Claude Sonnet 4] Test commit 4 (HEAD -> work-item-8)
+7120221 Author [GPT-4.1] Test commit 3
+ea03d91 Author [] Test commit 2
+f93fd8e Author [GPT-4o] Test commit 1
+dde0159 Copilot [] Test work item (#7) (origin/main, origin/HEAD)
+```

docs/source-control/git-guidance/README.md

@@ -254,6 +254,7 @@ The essential parts of a commit message are:
 
 * subject line: a short description of the commit, maximum 50 characters long
 * body (optional): a longer description of the commit, wrapped at 72 characters, separated from the subject line by a blank line
+* trailers (optional): additional metadata about the commit in the form of key-value pairs on separate lines such as `Co-authored-by: <name> <email>` that can be used to indicate co-authors, reviewers, or other relevant information
 
 You are free to structure commit messages; however, git commands like `git log` utilize above structure.
 Therefore, it can be helpful to follow a convention within your team and to utilize git best.
@@ -269,48 +270,7 @@ For more information on commit message conventions, see:
 * [How to Write Better Git Commit Messages](https://www.freecodecamp.org/news/how-to-write-better-git-commit-messages)
 * [Information in commit messages](https://wiki.openstack.org/wiki/GitCommitMessages#Information_in_commit_messages)
 * [On commit messages](http://who-t.blogspot.com/2009/12/on-commit-messages.html)
-
-### AI-Assisted Code Authorship
-
-When using AI tools to generate code, it can be beneficial to maintain transparency about authorship for accountability, code review, and auditing purposes. This can be done easily by using [Git trailers](https://git-scm.com/docs/git-interpret-trailers) that append structured metadata to the end of commit messages.
-
-#### Agentic Code Authorship
-
-When using agentic AI tools to generate code, such as the GitHub Coding Agent feature where a GitHub issue (such as a story or task) can be assigned to a software engineering bot that analyzes the request, creates a branch, writes commits, and opens a pull request, authorship is typically attributed using tool-specific mechanisms that follow conventions similar to pair programming. For example, the GitHub Coding Agent creates its commits using the agent as an author with the supervising person acknowledged using the `Co-authored-by` trailer in the commit message. This allows AI-generated code to be attributed to the agent while still giving credit (and accountability) to the person who supervised or initiated the task.
-
-#### IDE Assistant Attribution
-
-When using an AI coding assistant inside an IDE, such as GitHub Copilot in Visual Studio Code, consider providing attribution in cases when the commit consists of primarily AI-generated code. This might occur when:
-
-* More than 50% of the lines in the commit were generated by AI
-* The AI provided the core logic or algorithmic approach
-* Substantial code blocks were accepted from AI suggestions
-
-This can be done by appending one or more custom trailers in the commit message, such as:
-
-```text
-Assistant-model: GPT-4o
-```
-
-Because most Git tooling expects `Co-authored-by` trailers to be formatted as email addresses, you should use a different trailer key to avoid confusion and to distinguish authorship from assistance.
-
-Trailers can be added manually at the end of a commit message, or by using the `git commit` command with the `--trailer` option:
-
-```sh
-git commit --message "Implement feature" --trailer "Assistant-model: GPT-4o"
-```
-
-Trailers can be displayed using the [pretty formats](https://git-scm.com/docs/pretty-formats#Documentation/pretty-formats.txt-trailersoptions) option to `git log` command. For example, for a formatted history showing the hash, author name, and assistant models used for each commit:
-```sh
-git log --color --pretty=format:"%C(yellow)%h%C(reset) %C(blue)%an%C(reset) [%C(magenta)%(trailers:key=Assistant-model,valueonly=true,separator=%x2C)%C(reset)] %s%C(bold cyan)%d%C(reset)"
-```
-```text
-2100e6c Author [GPT-4.1,Claude Sonnet 4] Test commit 4 (HEAD -> work-item-8)
-7120221 Author [GPT-4.1] Test commit 3
-ea03d91 Author [] Test commit 2
-f93fd8e Author [GPT-4o] Test commit 1
-dde0159 Copilot [] Test work item (#7) (origin/main, origin/HEAD)
-```
+* [Git trailers](https://git-scm.com/docs/git-interpret-trailers)
 
 ## Managing Remotes