From 98c5b0e7b48a3b4a5abf87ffbe045c5114477d2f Mon Sep 17 00:00:00 2001 From: Even Stensberg Date: Thu, 12 Feb 2026 14:26:30 +0100 Subject: [PATCH 1/5] chore(docs): add AI_POLICY.md --- .github/AI_POLICY.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 .github/AI_POLICY.md diff --git a/.github/AI_POLICY.md b/.github/AI_POLICY.md new file mode 100644 index 0000000..29e4d61 --- /dev/null +++ b/.github/AI_POLICY.md @@ -0,0 +1,15 @@ +# Use of LLMs and similar tools + + +## Using AI to create commits + +Contributions that are based on AI-assisted tooling needs to be understood by the person contributing. If an issue, pull request or comment indicates that AI is used without a human understanding the concept, the corresponding issue, pull request or comment will ble closed. + +## Using AI to co-review + +If a user has created a pull request the author or reviewee is free to use LLM based tools to assist in reviewing the code changes. + +## Other + +**ALL** issues, pull requests and comments are required to be manually written by the author. If not, the maintainers in a repository will automatically delete/close the work done. If one really needs to use AI when interacting with webpack, it should be on an "assist" basis to fill inn small holes rather than creating content from scratch. + From f134d3a4f531168877396036cc1afa2e351eaa9e Mon Sep 17 00:00:00 2001 From: Even Stensberg Date: Thu, 12 Feb 2026 18:11:42 +0100 Subject: [PATCH 2/5] chore(docs): review --- .github/AI_POLICY.md | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/.github/AI_POLICY.md b/.github/AI_POLICY.md index 29e4d61..e8abac8 100644 --- a/.github/AI_POLICY.md +++ b/.github/AI_POLICY.md @@ -1,15 +1,11 @@ -# Use of LLMs and similar tools +# Use of AI tools and LLM based products -## Using AI to create commits +Contributions that are based on AI-assisted tooling needs to be understood by the person contributing. If an issue, pull request or comment indicates that AI is used without a human understanding the concept, the corresponding issue, pull request or comment will be closed. -Contributions that are based on AI-assisted tooling needs to be understood by the person contributing. If an issue, pull request or comment indicates that AI is used without a human understanding the concept, the corresponding issue, pull request or comment will ble closed. +If a user has created a pull request the author or reviewee is free to use LLM based tools to assist in reviewing the code changes. For instance, this could be to proof-read a script or documentation. -## Using AI to co-review +**ALL** issues, pull requests and comments are required to be manually written in some way by the author. If not, the maintainers in a repository will automatically delete/close the work done. If one really needs to use AI when interacting with webpack, it should be on an "assist" basis to fill inn small knowledge gaps. -If a user has created a pull request the author or reviewee is free to use LLM based tools to assist in reviewing the code changes. -## Other - -**ALL** issues, pull requests and comments are required to be manually written by the author. If not, the maintainers in a repository will automatically delete/close the work done. If one really needs to use AI when interacting with webpack, it should be on an "assist" basis to fill inn small holes rather than creating content from scratch. From 0bfbb2bb09d1d4aa35179207a950ff2b2b450379 Mon Sep 17 00:00:00 2001 From: Even Stensberg Date: Thu, 12 Feb 2026 18:13:50 +0100 Subject: [PATCH 3/5] chore(docs): review --- .github/AI_POLICY.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/AI_POLICY.md b/.github/AI_POLICY.md index e8abac8..5618c5f 100644 --- a/.github/AI_POLICY.md +++ b/.github/AI_POLICY.md @@ -3,9 +3,9 @@ Contributions that are based on AI-assisted tooling needs to be understood by the person contributing. If an issue, pull request or comment indicates that AI is used without a human understanding the concept, the corresponding issue, pull request or comment will be closed. -If a user has created a pull request the author or reviewee is free to use LLM based tools to assist in reviewing the code changes. For instance, this could be to proof-read a script or documentation. +If a user has created a pull request the author or reviewee, is allowed to use LLM based tools to assist in reviewing code changes. For instance, this could be to proof-read scripts or documentation. -**ALL** issues, pull requests and comments are required to be manually written in some way by the author. If not, the maintainers in a repository will automatically delete/close the work done. If one really needs to use AI when interacting with webpack, it should be on an "assist" basis to fill inn small knowledge gaps. +**ALL** issues, pull requests and comments are required to be manually written in some way by the author. If not, the maintainers in a repository will automatically delete/close the work done. If one really needs to use AI when interacting with webpack, it should be on an "assist-only" basis to fill inn small knowledge gaps, repetitive tasks or similar. From c330e7dc095995a3952ac57c62bb62f9a225b5a7 Mon Sep 17 00:00:00 2001 From: Even Stensberg Date: Thu, 12 Feb 2026 18:32:28 +0100 Subject: [PATCH 4/5] chore: add examples --- .github/AI_POLICY.md | 35 +++++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+) diff --git a/.github/AI_POLICY.md b/.github/AI_POLICY.md index 5618c5f..3b0c58f 100644 --- a/.github/AI_POLICY.md +++ b/.github/AI_POLICY.md @@ -7,5 +7,40 @@ If a user has created a pull request the author or reviewee, is allowed to use L **ALL** issues, pull requests and comments are required to be manually written in some way by the author. If not, the maintainers in a repository will automatically delete/close the work done. If one really needs to use AI when interacting with webpack, it should be on an "assist-only" basis to fill inn small knowledge gaps, repetitive tasks or similar. +**Examples of acceptable use of AI:** +> [!NOTE] +> Most use of AI should be done locally on your machine or setup. Do not create content based on AI (as explained in this document) in our repositories or community. +- Your pull request is done but you use AI to review your work before submitting a PR. +> Example prompt `> review my pull request and suggest improvements to grammar or code style`. + +- You are strugging to understand a concept such as `example.js` and ask AI to explain it to you on your local machine / environment. +> Example prompt `> explain test.js to me` + +- You use AI to create the basic functionality of a larger workload such as a function named `function toDO(){// implement me}`. +> Example prompt `> Create placeholder function that implements assertions for foo bar`. + +- You are writing documentation, you've filled inn the basic concepts and ask AI to suggest what else to mention. Note that this output needs to be written in a human form unless specifically given permission by any maintainer to use AI for this task. +> Example prompt `> Suggest additional information in point no.2 for me`. + + +**Examples of not how to use AI within webpack:** + +- You ask AI to create an issue for you in webpack without any context. +> Example prompt `> create an issue in webpack that I can solve.`. + +- You ask AI to fix an existing issue. +> Example prompt `> fix this error for me.`. + +- You ask AI to comment or reply to a comment on your behalf. +> Example prompt `> reply with a solution to person x.`. + +- You auto-fill our issue or pull request templates with AI written content. +> Example prompt `> create a pull request in webpack with my changes, describe what is done.` + +- Your work is heavily based on AI input and without any clear reason. +> Example prompt `> explain this to me and commit the correct code.` + +> [!IMPORTANT] +> __This policy does not only cover the webpack organization on GitHub, but on X, Discord and all other platforms used by the organization.__ \ No newline at end of file From a6f7e00513eaad23bf2174b601ae71ebe36004eb Mon Sep 17 00:00:00 2001 From: Even Stensberg Date: Thu, 12 Feb 2026 19:27:05 +0100 Subject: [PATCH 5/5] chore(docs): add headings --- .github/AI_POLICY.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/.github/AI_POLICY.md b/.github/AI_POLICY.md index 3b0c58f..248dee7 100644 --- a/.github/AI_POLICY.md +++ b/.github/AI_POLICY.md @@ -7,11 +7,12 @@ If a user has created a pull request the author or reviewee, is allowed to use L **ALL** issues, pull requests and comments are required to be manually written in some way by the author. If not, the maintainers in a repository will automatically delete/close the work done. If one really needs to use AI when interacting with webpack, it should be on an "assist-only" basis to fill inn small knowledge gaps, repetitive tasks or similar. -**Examples of acceptable use of AI:** +## **Examples of acceptable use of AI:** > [!NOTE] > Most use of AI should be done locally on your machine or setup. Do not create content based on AI (as explained in this document) in our repositories or community. + - Your pull request is done but you use AI to review your work before submitting a PR. > Example prompt `> review my pull request and suggest improvements to grammar or code style`. @@ -25,7 +26,7 @@ If a user has created a pull request the author or reviewee, is allowed to use L > Example prompt `> Suggest additional information in point no.2 for me`. -**Examples of not how to use AI within webpack:** +## **Examples of not how to use AI within webpack:** - You ask AI to create an issue for you in webpack without any context. > Example prompt `> create an issue in webpack that I can solve.`.