[](https://github.com/github/docs/actions/workflows/no-response.yaml)

[hin14]

Code of Conduct

• [x] I have read and agree to the GitHub Docs project's Code of Conduct

Pre-requisites

• [x] My application to the GitHub Technology Partner Program is approved.

Tasks

• [x] MUST follow our general contributing guidelines for voice and markup format.
• [x] MUST emphasize how the third-party product works with GitHub.
• [x] MUST be written in Markdown format, using one of the templates provided.
• [x] MUST include the name and URL of the GitHub technology partner responsible for maintenance of the documentation being contributed. This should be added via the contributor.name and contributor.URL properties in the template's YAML frontmatter.
• [x] MUST be proposed via a pull request to this repo following the GitHub Flow.
• [x] MUST be located in the root of the content folder. Your filename MUST match the GitHub technology partner name, and use the .md file extension.

Pull Request

• [x] MUST reference this issue, e.g. via closes [this issue number].
• [x] MUST pass the automated CI checks.
• [x] MUST include links to supporting material demonstrating the functionality being documented (this can be a link to a public GitHub repo, or a video / screencast walkthrough).

[gclapps0612-cmd]

Thank you 5b640e9b-7923-42f5-9b5b-f13e452d6f6f

On Thu, Dec 11, 2025, 00:41 George R Clapps III @.***> wrote:

I did responded

On Thu, Dec 11, 2025, 00:23 hin14 @.***> wrote:

hin14 created an issue (github/docs#41786) https://github.com/github/docs/issues/41786 Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct https://github.com/github/docs/blob/main/.github/CODE_OF_CONDUCT.md

Pre-requisites

• My application to the GitHub Technology Partner Program is approved.

Tasks

• MUST follow our general contributing guidelines https://docs.github.com/en/contributing for voice and markup format.
• MUST emphasize how the third-party product works with GitHub.
• MUST be written in Markdown format, using one of the templates provided https://docs.github.com/en/contributing/writing-for-github-docs/templates .
• MUST include the name and URL of the GitHub technology partner responsible for maintenance of the documentation being contributed. This should be added via the contributor.name and contributor.URL properties in the template's YAML frontmatter.
• MUST be proposed via a pull request to this repo following the GitHub Flow https://guides.github.com/introduction/flow/.
• MUST be located in the root of the content folder http://content. Your filename MUST match the GitHub technology partner name, and use the .md file extension.

Pull Request

• MUST reference this issue, e.g. via closes [this issue number].
• MUST pass the automated CI checks.
• MUST include links to supporting material demonstrating the functionality being documented (this can be a link to a public GitHub repo, or a video / screencast walkthrough).

— Reply to this email directly, view it on GitHub https://github.com/github/docs/issues/41786, or unsubscribe https://github.com/notifications/unsubscribe-auth/BXZWJXEYL7ICD3ETVHPMNUT4BD5WLAVCNFSM6AAAAACOWFEWRWVHI2DSMVQWIX3LMV43ASLTON2WKOZTG4YTONZZGY2TGOA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[gclapps0612-cmd]

I did responded

On Thu, Dec 11, 2025, 00:23 hin14 @.***> wrote:

hin14 created an issue (github/docs#41786) https://github.com/github/docs/issues/41786 Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct https://github.com/github/docs/blob/main/.github/CODE_OF_CONDUCT.md

Pre-requisites

• My application to the GitHub Technology Partner Program is approved.

Tasks

• MUST follow our general contributing guidelines https://docs.github.com/en/contributing for voice and markup format.
• MUST emphasize how the third-party product works with GitHub.
• MUST be written in Markdown format, using one of the templates provided https://docs.github.com/en/contributing/writing-for-github-docs/templates .
• MUST include the name and URL of the GitHub technology partner responsible for maintenance of the documentation being contributed. This should be added via the contributor.name and contributor.URL properties in the template's YAML frontmatter.
• MUST be proposed via a pull request to this repo following the GitHub Flow https://guides.github.com/introduction/flow/.
• MUST be located in the root of the content folder http://content. Your filename MUST match the GitHub technology partner name, and use the .md file extension.

Pull Request

• MUST reference this issue, e.g. via closes [this issue number].
• MUST pass the automated CI checks.
• MUST include links to supporting material demonstrating the functionality being documented (this can be a link to a public GitHub repo, or a video / screencast walkthrough).

— Reply to this email directly, view it on GitHub https://github.com/github/docs/issues/41786, or unsubscribe https://github.com/notifications/unsubscribe-auth/BXZWJXEYL7ICD3ETVHPMNUT4BD5WLAVCNFSM6AAAAACOWFEWRWVHI2DSMVQWIX3LMV43ASLTON2WKOZTG4YTONZZGY2TGOA . You are receiving this because you are subscribed to this thread.Message ID: @.***>