This is an automated email from the ASF dual-hosted git repository.
potiuk 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 6acd3d213c4 Add author-primary review-nudge/reviewer-ping triage
templates (#67428)
6acd3d213c4 is described below
commit 6acd3d213c45aaccee34583bf474fb382f556087
Author: Yeonguk Choo <[email protected]>
AuthorDate: Mon May 25 20:52:37 2026 +0900
Add author-primary review-nudge/reviewer-ping triage templates (#67428)
---
.../pr-management-triage-comment-templates.md | 36 ++++++++++++++++++++++
1 file changed, 36 insertions(+)
diff --git
a/.apache-steward-overrides/pr-management-triage-comment-templates.md
b/.apache-steward-overrides/pr-management-triage-comment-templates.md
index c669ff9540b..58c63782840 100644
--- a/.apache-steward-overrides/pr-management-triage-comment-templates.md
+++ b/.apache-steward-overrides/pr-management-triage-comment-templates.md
@@ -35,6 +35,7 @@
- [`reviewer-ping` (author-primary)](#reviewer-ping-author-primary)
- [`reviewer-ping` (reviewer-re-review)](#reviewer-ping-reviewer-re-review)
- [`mark-ready-with-ping`](#mark-ready-with-ping)
+ - [`request-author-confirmation`](#request-author-confirmation)
- [`stale-draft-close` (triaged)](#stale-draft-close-triaged)
- [`stale-draft-close` (untriaged)](#stale-draft-close-untriaged)
- [`inactive-to-draft`](#inactive-to-draft)
@@ -209,6 +210,14 @@ This is **not** a rejection — you're welcome to open a new
PR addressing the i
<ai_attribution_footer>
```
+### `review-nudge` (author-primary)
+
+```markdown
+@<author> — This PR has new commits since the last review requesting changes
from <reviewer_logins>. Could you address the outstanding review comments and
either push a fix or reply in each thread explaining why the feedback doesn't
apply? When you believe the threads are resolved, please mark them as resolved
and ping the reviewer (<reviewer_logins>) — they'll either re-review or hand
the PR back to the queue. Thanks!
+
+<ai_attribution_footer>
+```
+
### `review-nudge` (reviewer-re-review)
```markdown
@@ -217,6 +226,14 @@ This is **not** a rejection — you're welcome to open a new
PR addressing the i
<ai_attribution_footer>
```
+### `reviewer-ping` (author-primary)
+
+```markdown
+@<author> — There are <N> unresolved review thread(s) on this PR from
<reviewer_logins>. Could you either push a fix or reply in each thread
explaining why the feedback doesn't apply? When you believe the feedback is
addressed, please mark the threads as resolved and ping the reviewer
(<reviewer_logins>) for a final look. Thanks!
+
+<ai_attribution_footer>
+```
+
### `reviewer-ping` (reviewer-re-review)
```markdown
@@ -237,6 +254,25 @@ This is **not** a rejection — you're welcome to open a new
PR addressing the i
<ai_attribution_footer>
```
+### `request-author-confirmation`
+
+The body **must** include the literal marker string
+`ready for maintainer review confirmation` verbatim — the
+framework's
+[`viewer_confirmation_request_present`](../.claude/skills/pr-management-triage/classify-and-act.md#viewer_confirmation_request_present)
+precondition searches for that exact text. Do not paraphrase
+that string when adapting the rest of the body.
+
+```markdown
+@<author> — There are <N> unresolved review thread(s) on this PR, and you have
engaged with each one (post-review commits and/or in-thread replies). Could you
confirm whether you believe the feedback is fully addressed and the PR is ready
for maintainer review confirmation?
+
+If yes, reply here (a short "yes / ready" is fine) and an Apache Airflow
maintainer will pick the PR up from the review queue on the next sweep.
+
+If you are still working on a thread, please reply with what is outstanding so
the threads stay unresolved on purpose.
+
+<ai_attribution_footer>
+```
+
### `stale-draft-close` (triaged)
```markdown
