From 8e1a518ea5d9cb4a47c3211f6bf121914472164c Mon Sep 17 00:00:00 2001 From: Kirk Waiblinger <53019676+kirkwaiblinger@users.noreply.github.com> Date: Wed, 10 Dec 2025 07:24:36 -0700 Subject: [PATCH 1/2] docs: document expectations around AI use --- docs/contributing/Pull_Requests.mdx | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/docs/contributing/Pull_Requests.mdx b/docs/contributing/Pull_Requests.mdx index e1aa475654b7..de91f96072e0 100644 --- a/docs/contributing/Pull_Requests.mdx +++ b/docs/contributing/Pull_Requests.mdx @@ -25,6 +25,23 @@ Please don't: - Comment on a closed PR - Reasoning: It is much easier for maintainers to not lose track of things if they are posted as issues. If you think there's a bug in typescript-eslint, the right way to ask is to [file a new issue](https://github.com/typescript-eslint/typescript-eslint/issues/new/choose). The issue templates include helpful & necessary practices such as making sure you're on the latest version of all our packages. You can provide the link to the relevant PR to add more context. +:::warning Contribution standards in the era of AI + +We reserve the right to close PRs and issues that we deem to be poor quality and/or which we deem will take an undue amount of maintainer effort to make progress on. + +With the rise of AI-assisted coding tools, it has become trivial to generate large amounts of low-quality contributions, for PRs and issues. +Parsing, reviewing, and iterating on these in good faith takes up much more maintainer bandwidth than traditional contributions, taking away bandwidth from other opportunities to advance typescript-eslint. + +While we cannot and will not attempt to ban contributions which make use of AI, we ask that you use AI responsibly: + +- Always review AI-generated content closely +- Only use AI for contributions that you would understand well enough to champion and respond to feedback on without making use of AI +- Do not ignore our issue and PR templates + +Don't let this dissuade you from contributing to typescript-eslint! We are generally more than happy to assist new contributors and help them improve at our repo. We just are not interested in babysitting anyone's LLM instances. + +::: + ## Testing Changes ### Code Coverage From 6deb5e3c78bfdc92677abc3e9db96edc72d5d18e Mon Sep 17 00:00:00 2001 From: Kirk Waiblinger <53019676+kirkwaiblinger@users.noreply.github.com> Date: Mon, 15 Dec 2025 13:20:55 -0700 Subject: [PATCH 2/2] pr feedback --- docs/contributing/Pull_Requests.mdx | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/docs/contributing/Pull_Requests.mdx b/docs/contributing/Pull_Requests.mdx index de91f96072e0..69d07793ed79 100644 --- a/docs/contributing/Pull_Requests.mdx +++ b/docs/contributing/Pull_Requests.mdx @@ -34,11 +34,16 @@ Parsing, reviewing, and iterating on these in good faith takes up much more main While we cannot and will not attempt to ban contributions which make use of AI, we ask that you use AI responsibly: -- Always review AI-generated content closely -- Only use AI for contributions that you would understand well enough to champion and respond to feedback on without making use of AI +- Always review AI-generated content closely before submitting a PR +- Only use AI to assist in contributions that you would understand well enough to champion and respond to feedback on without making use of AI - Do not ignore our issue and PR templates +- Especially avoid AI-generated PR descriptions. + These tend to just be nearly-verbatim descriptions of the code diff, which add no value to the PR. + Instead, we ask that you summarize the PR succinctly in your own words, relying on your own understanding of the code. -Don't let this dissuade you from contributing to typescript-eslint! We are generally more than happy to assist new contributors and help them improve at our repo. We just are not interested in babysitting anyone's LLM instances. +Don't let this dissuade you from contributing to typescript-eslint! +We very much welcome new contributors and are happy to help them improve. +We just are not happy to spend our time working with a contributor who primarily defers to an AI coding assistant; at that point it'd be a better use of our time to prompt the LLM ourselves. :::