From 6153569afb6f189fff3712a024dc069051368df2 Mon Sep 17 00:00:00 2001 From: Paillat-dev Date: Thu, 9 Jul 2026 15:11:42 +0200 Subject: [PATCH 01/17] docs: First AI policy draft --- CONTRIBUTING.md | 44 +++++++++++++++++++++++++++++++------------- 1 file changed, 31 insertions(+), 13 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 627c7717b1..1591f7d801 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -29,19 +29,19 @@ Please be aware of the following things when filing bug reports. 3. Make sure to provide enough information to make the issue workable. The issue template will generally walk you through the process but they are enumerated here as well: - - A **summary** of your bug report. This is generally a quick sentence or two to - describe the issue in human terms. - - Guidance on **how to reproduce the issue**. Ideally, this should have a small code - sample that allows us to run and see the issue for ourselves to debug. **Please - make sure that the token is not displayed**. If you cannot provide a code snippet, - then let us know what the steps were, how often it happens, etc. - - Tell us **what you expected to happen**. That way we can meet that expectation. - - Tell us **what actually happens**. What ends up happening in reality? It's not - helpful to say "it fails" or "it doesn't work". Say _how_ it failed, do you get an - exception? Does it hang? How are the expectations different from reality? - - Tell us **information about your environment**. What version of Pycord are you - using? How was it installed? What operating system are you running on? These are - valuable questions and information that we use. + - A **summary** of your bug report. This is generally a quick sentence or two to + describe the issue in human terms. + - Guidance on **how to reproduce the issue**. Ideally, this should have a small code + sample that allows us to run and see the issue for ourselves to debug. **Please + make sure that the token is not displayed**. If you cannot provide a code snippet, + then let us know what the steps were, how often it happens, etc. + - Tell us **what you expected to happen**. That way we can meet that expectation. + - Tell us **what actually happens**. What ends up happening in reality? It's not + helpful to say "it fails" or "it doesn't work". Say _how_ it failed, do you get an + exception? Does it hang? How are the expectations different from reality? + - Tell us **information about your environment**. What version of Pycord are you + using? How was it installed? What operating system are you running on? These are + valuable questions and information that we use. If the bug report is missing this information then it'll take us longer to fix the issue. We will probably ask for clarification, and barring that if no response was given @@ -82,3 +82,21 @@ different to others. We don't limit nor deny your pulls when you're using another style although, please make sure it is appropriate and makes sense in this library. + +### AI Usage Policy + +The use of LLMs or other AI tools for any kind of partial or complete interaction or contribution (included but not +limited to writing code, documentation or discussing with maintainers) must be disclosed at all times. The disclosure +must include what tools what used and within which scope. + +The use of fully autonomous LLMs or other AI tools to perform the action of opening issues or pull requests is +forbidden. + +Failure to disclose your AI use or to follow this policy may result in a temporary or permanent ban from our +organization. + +The use of LLMs or AI tools by new contributors is highly discouraged, and may result to direct closure of your issue +or pull request. + +Furthermore, as outlined earlier in § "Licensing", by submitting a pull request, you agree that you hold the copyright +on your contribution. From 6684449878108e5b0b7f97bfa9217ccf3974cfa5 Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Thu, 9 Jul 2026 13:14:46 +0000 Subject: [PATCH 02/17] style(pre-commit): auto fixes from pre-commit.com hooks --- CONTRIBUTING.md | 49 +++++++++++++++++++++++++------------------------ 1 file changed, 25 insertions(+), 24 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 1591f7d801..4f5b66691e 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -29,19 +29,19 @@ Please be aware of the following things when filing bug reports. 3. Make sure to provide enough information to make the issue workable. The issue template will generally walk you through the process but they are enumerated here as well: - - A **summary** of your bug report. This is generally a quick sentence or two to - describe the issue in human terms. - - Guidance on **how to reproduce the issue**. Ideally, this should have a small code - sample that allows us to run and see the issue for ourselves to debug. **Please - make sure that the token is not displayed**. If you cannot provide a code snippet, - then let us know what the steps were, how often it happens, etc. - - Tell us **what you expected to happen**. That way we can meet that expectation. - - Tell us **what actually happens**. What ends up happening in reality? It's not - helpful to say "it fails" or "it doesn't work". Say _how_ it failed, do you get an - exception? Does it hang? How are the expectations different from reality? - - Tell us **information about your environment**. What version of Pycord are you - using? How was it installed? What operating system are you running on? These are - valuable questions and information that we use. + - A **summary** of your bug report. This is generally a quick sentence or two to + describe the issue in human terms. + - Guidance on **how to reproduce the issue**. Ideally, this should have a small code + sample that allows us to run and see the issue for ourselves to debug. **Please + make sure that the token is not displayed**. If you cannot provide a code snippet, + then let us know what the steps were, how often it happens, etc. + - Tell us **what you expected to happen**. That way we can meet that expectation. + - Tell us **what actually happens**. What ends up happening in reality? It's not + helpful to say "it fails" or "it doesn't work". Say _how_ it failed, do you get an + exception? Does it hang? How are the expectations different from reality? + - Tell us **information about your environment**. What version of Pycord are you + using? How was it installed? What operating system are you running on? These are + valuable questions and information that we use. If the bug report is missing this information then it'll take us longer to fix the issue. We will probably ask for clarification, and barring that if no response was given @@ -85,18 +85,19 @@ sure it is appropriate and makes sense in this library. ### AI Usage Policy -The use of LLMs or other AI tools for any kind of partial or complete interaction or contribution (included but not -limited to writing code, documentation or discussing with maintainers) must be disclosed at all times. The disclosure -must include what tools what used and within which scope. +The use of LLMs or other AI tools for any kind of partial or complete interaction or +contribution (included but not limited to writing code, documentation or discussing with +maintainers) must be disclosed at all times. The disclosure must include what tools what +used and within which scope. -The use of fully autonomous LLMs or other AI tools to perform the action of opening issues or pull requests is -forbidden. +The use of fully autonomous LLMs or other AI tools to perform the action of opening +issues or pull requests is forbidden. -Failure to disclose your AI use or to follow this policy may result in a temporary or permanent ban from our -organization. +Failure to disclose your AI use or to follow this policy may result in a temporary or +permanent ban from our organization. -The use of LLMs or AI tools by new contributors is highly discouraged, and may result to direct closure of your issue -or pull request. +The use of LLMs or AI tools by new contributors is highly discouraged, and may result to +direct closure of your issue or pull request. -Furthermore, as outlined earlier in § "Licensing", by submitting a pull request, you agree that you hold the copyright -on your contribution. +Furthermore, as outlined earlier in § "Licensing", by submitting a pull request, you +agree that you hold the copyright on your contribution. From b59479d005226cbcdab7ce76ef7b818749180832 Mon Sep 17 00:00:00 2001 From: Paillat-dev Date: Thu, 9 Jul 2026 15:16:43 +0200 Subject: [PATCH 03/17] fix: Various formattings --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 4f5b66691e..5b579661bd 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -83,7 +83,7 @@ different to others. We don't limit nor deny your pulls when you're using another style although, please make sure it is appropriate and makes sense in this library. -### AI Usage Policy +## AI Usage Policy The use of LLMs or other AI tools for any kind of partial or complete interaction or contribution (included but not limited to writing code, documentation or discussing with @@ -99,5 +99,5 @@ permanent ban from our organization. The use of LLMs or AI tools by new contributors is highly discouraged, and may result to direct closure of your issue or pull request. -Furthermore, as outlined earlier in § "Licensing", by submitting a pull request, you +Furthermore, as outlined earlier in §"Licensing", by submitting a pull request, you agree that you hold the copyright on your contribution. From 04f483130a3653c8b76c58b935f241e09b2546b0 Mon Sep 17 00:00:00 2001 From: Paillat-dev Date: Thu, 9 Jul 2026 15:20:43 +0200 Subject: [PATCH 04/17] fix: Squ1d comments Co-authored-by: JustaSqu1d <89910983+justasqu1d@users.noreply.github.com> --- CONTRIBUTING.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 5b579661bd..bf6bd70909 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -86,9 +86,9 @@ sure it is appropriate and makes sense in this library. ## AI Usage Policy The use of LLMs or other AI tools for any kind of partial or complete interaction or -contribution (included but not limited to writing code, documentation or discussing with -maintainers) must be disclosed at all times. The disclosure must include what tools what -used and within which scope. +contribution (including but not limited to the following: writing code/documentation or +discussing with maintainers) must be disclosed at all times. The disclosure must include +what tools what used and to what scopes they were used. The use of fully autonomous LLMs or other AI tools to perform the action of opening issues or pull requests is forbidden. @@ -99,5 +99,5 @@ permanent ban from our organization. The use of LLMs or AI tools by new contributors is highly discouraged, and may result to direct closure of your issue or pull request. -Furthermore, as outlined earlier in §"Licensing", by submitting a pull request, you +Furthermore, as outlined earlier in §"Licensing," by submitting a pull request, you agree that you hold the copyright on your contribution. From 351292b50865382380ceaf299cf455855c447c6f Mon Sep 17 00:00:00 2001 From: Paillat-dev Date: Thu, 9 Jul 2026 15:25:31 +0200 Subject: [PATCH 05/17] docs: Add translation note --- CONTRIBUTING.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index bf6bd70909..2ccc10c572 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -90,6 +90,11 @@ contribution (including but not limited to the following: writing code/documenta discussing with maintainers) must be disclosed at all times. The disclosure must include what tools what used and to what scopes they were used. +Using LLMs or other AI tools for translation, for example, if you are not a native +English speaker, is discouraged. It can distort your intended meaning and make a +human-written contribution look AI-generated. Please use a non-LLM-based translation +tool instead. + The use of fully autonomous LLMs or other AI tools to perform the action of opening issues or pull requests is forbidden. From 919c1e095fab557cf3311081f72caedd9745d197 Mon Sep 17 00:00:00 2001 From: Paillat-dev Date: Thu, 9 Jul 2026 15:27:30 +0200 Subject: [PATCH 06/17] docs: Vmphase fixes Co-authored-by: Michael --- CONTRIBUTING.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 2ccc10c572..366565adb9 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -95,14 +95,14 @@ English speaker, is discouraged. It can distort your intended meaning and make a human-written contribution look AI-generated. Please use a non-LLM-based translation tool instead. -The use of fully autonomous LLMs or other AI tools to perform the action of opening -issues or pull requests is forbidden. +The use of fully autonomous LLMs or other AI tools to open issues or pull requests is +forbidden. Failure to disclose your AI use or to follow this policy may result in a temporary or permanent ban from our organization. -The use of LLMs or AI tools by new contributors is highly discouraged, and may result to -direct closure of your issue or pull request. +The use of LLMs or AI tools by new contributors is highly discouraged, and may result in +the direct closure of your issue or pull request. Furthermore, as outlined earlier in §"Licensing," by submitting a pull request, you agree that you hold the copyright on your contribution. From 344c7f848d18c03c9f17d9f821849e9a1a4d684f Mon Sep 17 00:00:00 2001 From: Paillat-dev Date: Thu, 9 Jul 2026 15:33:08 +0200 Subject: [PATCH 07/17] docs: Non-disclosure is already not following --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 366565adb9..39586e0126 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -98,8 +98,8 @@ tool instead. The use of fully autonomous LLMs or other AI tools to open issues or pull requests is forbidden. -Failure to disclose your AI use or to follow this policy may result in a temporary or -permanent ban from our organization. +Failure to follow this policy may result in a temporary or permanent ban from our +organization. The use of LLMs or AI tools by new contributors is highly discouraged, and may result in the direct closure of your issue or pull request. From cb0dfc53c1ddc21a912be7982514a82d87b69463 Mon Sep 17 00:00:00 2001 From: Paillat-dev Date: Thu, 9 Jul 2026 15:40:36 +0200 Subject: [PATCH 08/17] docs: Vmphase fixes 2 Co-authored-by: Michael --- CONTRIBUTING.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 39586e0126..5b37488502 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -88,12 +88,11 @@ sure it is appropriate and makes sense in this library. The use of LLMs or other AI tools for any kind of partial or complete interaction or contribution (including but not limited to the following: writing code/documentation or discussing with maintainers) must be disclosed at all times. The disclosure must include -what tools what used and to what scopes they were used. +what tools were used and to what scopes they were used. -Using LLMs or other AI tools for translation, for example, if you are not a native -English speaker, is discouraged. It can distort your intended meaning and make a -human-written contribution look AI-generated. Please use a non-LLM-based translation -tool instead. +If you are not a native English speaker, using LLMs or other AI tools for translation is +discouraged. It can distort your intended meaning and make a human-written contribution +look AI-generated. Please use a non-LLM-based translation tool instead. The use of fully autonomous LLMs or other AI tools to open issues or pull requests is forbidden. From c8e59687c937a6d14188b9658ca5565bb1bf0602 Mon Sep 17 00:00:00 2001 From: Paillat-dev Date: Thu, 9 Jul 2026 15:45:32 +0200 Subject: [PATCH 09/17] docs: Fix "Licensing" heading level --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 5b37488502..081fcb12f8 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -60,7 +60,7 @@ In some cases, it might be necessary to ignore type checker warnings for one rea another. If that is the case, it is **required** that a comment is left explaining why you are deciding to ignore type checking warnings. -### Licensing +## Licensing By submitting a pull request, you agree that; 1) You hold the copyright on all submitted code inside said pull request; 2) You agree to transfer all rights to the owner of this From cd529f5c0f23b66e18255bce60cdce192b615768 Mon Sep 17 00:00:00 2001 From: Paillat-dev Date: Thu, 9 Jul 2026 15:56:23 +0200 Subject: [PATCH 10/17] docs: Lala fixes Co-authored-by: Lala Sabathil --- CONTRIBUTING.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 081fcb12f8..943d5a4a52 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -92,10 +92,11 @@ what tools were used and to what scopes they were used. If you are not a native English speaker, using LLMs or other AI tools for translation is discouraged. It can distort your intended meaning and make a human-written contribution -look AI-generated. Please use a non-LLM-based translation tool instead. +look AI-generated. Please use a non-LLM-based translation tool like https://deepl.com +instead. The use of fully autonomous LLMs or other AI tools to open issues or pull requests is -forbidden. +strictly forbidden. Failure to follow this policy may result in a temporary or permanent ban from our organization. From 2e02e7cee6ba265ace4706978888aa6db2dfb89a Mon Sep 17 00:00:00 2001 From: Paillat-dev Date: Thu, 9 Jul 2026 16:09:52 +0200 Subject: [PATCH 11/17] docs: Lala fixes 2 Co-authored-by: Lala Sabathil --- CONTRIBUTING.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 943d5a4a52..f81df8f3ea 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -105,4 +105,6 @@ The use of LLMs or AI tools by new contributors is highly discouraged, and may r the direct closure of your issue or pull request. Furthermore, as outlined earlier in §"Licensing," by submitting a pull request, you -agree that you hold the copyright on your contribution. +agree that you hold the copyright on your contribution; and that you understand how your +submitted code works and are able to explain its purpose, behavior, and impact when +requested. From 154d485202c41894558d12d5e4fe34532f95a91e Mon Sep 17 00:00:00 2001 From: Paillat-dev Date: Thu, 9 Jul 2026 16:11:39 +0200 Subject: [PATCH 12/17] docs: Squid & Vmphase fixes Co-authored-by: JustaSqu1d <89910983+justasqu1d@users.noreply.github.com> Co-authored-by: vmphase --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index f81df8f3ea..776de8c210 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -87,8 +87,8 @@ sure it is appropriate and makes sense in this library. The use of LLMs or other AI tools for any kind of partial or complete interaction or contribution (including but not limited to the following: writing code/documentation or -discussing with maintainers) must be disclosed at all times. The disclosure must include -what tools were used and to what scopes they were used. +discussing with maintainers) must be disclosed at all times. The disclosure must specify +the tools used and the scope of their application. If you are not a native English speaker, using LLMs or other AI tools for translation is discouraged. It can distort your intended meaning and make a human-written contribution From 74b44377b22c0d6b2fad1eb00ab68407142aa701 Mon Sep 17 00:00:00 2001 From: Paillat-dev Date: Thu, 9 Jul 2026 16:57:54 +0200 Subject: [PATCH 13/17] docs: Squid fixes 2 Co-authored-by: JustaSqu1d <89910983+justasqu1d@users.noreply.github.com> --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 776de8c210..54532e76ab 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -92,8 +92,8 @@ the tools used and the scope of their application. If you are not a native English speaker, using LLMs or other AI tools for translation is discouraged. It can distort your intended meaning and make a human-written contribution -look AI-generated. Please use a non-LLM-based translation tool like https://deepl.com -instead. +look AI-generated. Please use a non-LLM-based translation tool like +[DeepL](https://deepl.com) instead. The use of fully autonomous LLMs or other AI tools to open issues or pull requests is strictly forbidden. From 9c7027cd1b8bd670ea2749fa1380f20b6b395c51 Mon Sep 17 00:00:00 2001 From: Paillat-dev Date: Thu, 9 Jul 2026 16:59:24 +0200 Subject: [PATCH 14/17] docs: Squid & Vmphase fixes 2 Co-authored-by: vmphase Co-authored-by: JustaSqu1d <89910983+justasqu1d@users.noreply.github.com> --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 54532e76ab..f303fabc16 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -86,7 +86,7 @@ sure it is appropriate and makes sense in this library. ## AI Usage Policy The use of LLMs or other AI tools for any kind of partial or complete interaction or -contribution (including but not limited to the following: writing code/documentation or +contribution (including but not limited to the following: code, documentation, or discussing with maintainers) must be disclosed at all times. The disclosure must specify the tools used and the scope of their application. From 7122b2e364c745f5d75d6cb923ff3bc6f102d12f Mon Sep 17 00:00:00 2001 From: Paillat-dev Date: Thu, 9 Jul 2026 17:14:17 +0200 Subject: [PATCH 15/17] docs: Squid fixes 3 Co-authored-by: JustaSqu1d <89910983+justasqu1d@users.noreply.github.com> --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index f303fabc16..83b6dbf969 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -87,8 +87,8 @@ sure it is appropriate and makes sense in this library. The use of LLMs or other AI tools for any kind of partial or complete interaction or contribution (including but not limited to the following: code, documentation, or -discussing with maintainers) must be disclosed at all times. The disclosure must specify -the tools used and the scope of their application. +discussions with maintainers) must be disclosed at all times. The disclosure must +specify the tools used and the scope of their application. If you are not a native English speaker, using LLMs or other AI tools for translation is discouraged. It can distort your intended meaning and make a human-written contribution From 68a500baed39b515b40c73397d753714d3836511 Mon Sep 17 00:00:00 2001 From: Lala Sabathil Date: Sun, 12 Jul 2026 09:14:14 +0200 Subject: [PATCH 16/17] Update CONTRIBUTING.md Co-authored-by: Ice Wolfy <44532864+Icebluewolf@users.noreply.github.com> Signed-off-by: Lala Sabathil --- CONTRIBUTING.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 83b6dbf969..a12e07be3c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -85,10 +85,15 @@ sure it is appropriate and makes sense in this library. ## AI Usage Policy -The use of LLMs or other AI tools for any kind of partial or complete interaction or -contribution (including but not limited to the following: code, documentation, or -discussions with maintainers) must be disclosed at all times. The disclosure must -specify the tools used and the scope of their application. +The use of LLMs or other AI tools must be disclosed at all times. +Disclosure is required for any interaction or contribution which includes but is not limited to: +- Modifying Code +- Modifying Documentation +- Discussion with maintainers +- Issue bodies and comments +- Pull Request bodies and comments +The disclosure must specify the tools used and the scope of their application. +The primary location of disclosure should be in the body of Issues and Pull Requests. If you are not a native English speaker, using LLMs or other AI tools for translation is discouraged. It can distort your intended meaning and make a human-written contribution From 42f8dd89a836813a2cd646d99a928ca65cada25c Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Sun, 12 Jul 2026 07:14:47 +0000 Subject: [PATCH 17/17] style(pre-commit): auto fixes from pre-commit.com hooks --- CONTRIBUTING.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index a12e07be3c..40264247a4 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -85,15 +85,16 @@ sure it is appropriate and makes sense in this library. ## AI Usage Policy -The use of LLMs or other AI tools must be disclosed at all times. -Disclosure is required for any interaction or contribution which includes but is not limited to: +The use of LLMs or other AI tools must be disclosed at all times. Disclosure is required +for any interaction or contribution which includes but is not limited to: + - Modifying Code - Modifying Documentation - Discussion with maintainers - Issue bodies and comments -- Pull Request bodies and comments -The disclosure must specify the tools used and the scope of their application. -The primary location of disclosure should be in the body of Issues and Pull Requests. +- Pull Request bodies and comments The disclosure must specify the tools used and the + scope of their application. The primary location of disclosure should be in the body + of Issues and Pull Requests. If you are not a native English speaker, using LLMs or other AI tools for translation is discouraged. It can distort your intended meaning and make a human-written contribution