This is an automated email from the ASF dual-hosted git repository.

jedcunningham pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/main by this push:
     new 57d9e3980e9 Tell agents to check for an existing PR before starting an 
issue (#67914)
57d9e3980e9 is described below

commit 57d9e3980e92a3f87201d0fd4fa80721b715e2d7
Author: Jed Cunningham <[email protected]>
AuthorDate: Tue Jun 2 16:24:09 2026 -0600

    Tell agents to check for an existing PR before starting an issue (#67914)
---
 AGENTS.md | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/AGENTS.md b/AGENTS.md
index 92fab69a65b..a27c8868967 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -226,6 +226,17 @@ any other variant), **translate it to the `upstream` 
convention** in what you
 propose to the user, rather than perpetuating the old name. Flag the stale
 documentation so it can be fixed in a follow-up.
 
+### Before starting: check for an existing PR
+
+Before working on an issue, check for open PRs already addressing it
+(`gh pr list --search "<issue number or keywords>"`, and look for `closes:`
+/ `fixes:` references). Airflow allows parallel work — "better PR wins"
+(see `contributing-docs/04_how_to_contribute.rst`) — but it is not the
+default: prefer reviewing and building on an existing PR. Open a separate
+one only *if your approach is genuinely different*. Do not blindly open
+another near-identical PR for an issue that already has one (or several) —
+that just adds reviewer noise.
+
 ### Creating Pull Requests
 
 **Always push to the user's fork (`origin`)**, not to `upstream` 
(`apache/airflow`).

Reply via email to