This is an automated email from the ASF dual-hosted git repository.
choo121600 pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow-steward.git
The following commit(s) were added to refs/heads/main by this push:
new 6e00a3f docs(pr-management-triage): drop stale mark-ready-with-ping
refs (#285)
6e00a3f is described below
commit 6e00a3f8c3e3f312e8b70cbecd43d3f41dd27a75
Author: Jarek Potiuk <[email protected]>
AuthorDate: Mon May 25 20:53:52 2026 +0200
docs(pr-management-triage): drop stale mark-ready-with-ping refs (#285)
`mark-ready-with-ping` was the single-sweep precursor to the
two-sweep flow (`request-author-confirmation` → `mark-ready`
label only). The action was deprecated and its template body
removed when the two-sweep flow landed, but three references
to it survived in comment-templates.md:
- The `<reviewers>` placeholder bullet ("Use in reviewer-re-
review variants and `mark-ready-with-ping` only") — line 23.
- The Reviewer-mention policy prose ("...the reviewer-re-review
variants and `mark-ready-with-ping`") — line 61.
- The placeholder-reference table's "Use in" cell — line 78.
Drop each. The historical mention in
pr-management-triage/rationale.md (which explains *why* the
single-sweep action was retired) stays — load-bearing context,
not stale documentation.
Generated-by: Claude (Opus 4.7)
---
.claude/skills/pr-management-triage/comment-templates.md | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/.claude/skills/pr-management-triage/comment-templates.md
b/.claude/skills/pr-management-triage/comment-templates.md
index 2d4895c..4be07cb 100644
--- a/.claude/skills/pr-management-triage/comment-templates.md
+++ b/.claude/skills/pr-management-triage/comment-templates.md
@@ -20,9 +20,9 @@ Placeholders:
- `<flagged_count>` — number of currently-flagged PRs by this
author (for the `close` template)
- `<reviewers>` — space-separated `@login` mentions. **Use in
- reviewer-re-review variants and `mark-ready-with-ping` only**
- — those templates address the reviewer as the next-action
- recipient, so `@`-pinging them is appropriate.
+ reviewer-re-review variants only** — those templates address
+ the reviewer as the next-action recipient, so `@`-pinging
+ them is appropriate.
- `<reviewer_logins>` — comma-separated backtick-quoted logins
(e.g. `` `phanikumv` ``, `` `phanikumv`, `eladkal` ``) —
**no `@`-pings**. Use in author-primary templates
@@ -57,9 +57,9 @@ When a comment's only addressee is the PR author (the
and `review-nudge` author-primary templates), the body references
the reviewer **without** `@`-mentioning them. The default
`<reviewers>` placeholder renders as `@login` and is appropriate
-when the reviewer is one of the message's addressees (e.g. the
-reviewer-re-review variants and `mark-ready-with-ping`). In
-author-primary templates we use a different placeholder,
+when the reviewer is one of the message's addressees (the
+reviewer-re-review variants). In author-primary templates we
+use a different placeholder,
`<reviewer_logins>`, that renders the same logins **as
backtick-quoted code** (e.g. `` `phanikumv` ``,
`` `phanikumv`, `eladkal` ``) — recognisable as a GitHub handle
@@ -75,7 +75,7 @@ than by the bot.
| Placeholder | Renders as | Use in |
|---|---|---|
-| `<reviewers>` | `@login [, @login ...]` | reviewer-re-review variants,
`mark-ready-with-ping` |
+| `<reviewers>` | `@login [, @login ...]` | reviewer-re-review variants |
| `<reviewer_logins>` | `` `login` [, `login` ...] `` (no `@`) |
`request-author-confirmation`, `reviewer-ping` (author-primary), `review-nudge`
(author-primary) |
---
