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 11f515a4b7a Keep contributor testing comments short on providers
testing issues (#76772)
11f515a4b7a is described below
commit 11f515a4b7ae515d3e4383279faa8e0164ddbdd6
Author: Jarek Potiuk <[email protected]>
AuthorDate: Sat Nov 14 01:45:02 2026 +0100
Keep contributor testing comments short on providers testing issues (#76772)
A providers testing issue collects comments from dozens of contributors.
Long, unfolded test reports bury the verdicts the release manager is
scanning for, so the agent-drafted comment now shows only a one-line
verdict and keeps the evidence one click away.
Generated-by: Claude Opus 5
---
.apache-magpie-overrides/release-verify-rc.md | 21 +++++++++++++++++++--
1 file changed, 19 insertions(+), 2 deletions(-)
diff --git a/.apache-magpie-overrides/release-verify-rc.md
b/.apache-magpie-overrides/release-verify-rc.md
index 318c8d1269f..2fbfd4b7b3d 100644
--- a/.apache-magpie-overrides/release-verify-rc.md
+++ b/.apache-magpie-overrides/release-verify-rc.md
@@ -100,8 +100,25 @@ Once the user says the Dag passed:
editing, change only `[ ]` → `[x]` on lines ending in `: @<handle>` for PRs
verified
in step B, and abort if the number of matched lines differs from what was
reported.
2. **Draft the testing-issue comment (confirm first)** listing what was tested
per
- provider, including changes that are in the wave but missing from the
issue. End
- it with the `Drafted-by:` footer.
+ provider, including changes that are in the wave but missing from the
issue. The
+ issue collects comments from many contributors, so keep it to one visible
line:
+ - A one-sentence verdict, e.g. `Tested my changes against the RC
distributions in
+ Breeze. Every check passed. ✅`
+ - Everything else inside one `<details><summary>Testing details (setup,
results per
+ PR, test Dag source)</summary>` block. Leave a blank line after
`</summary>` and
+ before `</details>` so the Markdown inside renders. Put these in the
block, in order:
+ - `### Setup`: where the distributions came from and what was verified
about
+ them, the Airflow version, the exact `breeze start-airflow` command,
and how the
+ test Dag works.
+ - `### Results`: one bold heading per PR (`**#NNNNN <provider>
<version>rcN:
+ <title>**`, one bullet per provider for a PR that touches several),
saying
+ what was exercised and what was asserted. Use a table when several
variants
+ are checked. Quote task-log lines only from logs the user supplied —
never
+ invent log output. Mark a tested provider that is excluded from the
wave as
+ such, and leave its box unticked.
+ - The test Dag source in a nested `<details><summary>Test Dag
source</summary>`
+ block.
+ - Below the block, the `Drafted-by:` footer.
3. When the user drafts their `[VOTE]` reply, mention that they used this
check to
test all their changes in the candidate.
4. Offer cleanup: delete the downloaded wheels and the verification Dag, and
suggest
