The GitHub Actions job "prek" on airflow-steward.git/main has failed.
Run started by GitHub user potiuk (triggered by potiuk).

Head commit for run:
10624e254534b2a9ef79370b3400df3af743e3ab / Jarek Potiuk <[email protected]>
feat(gmail-threading): prefer the primary reporter thread over a 
forwarder/relay thread (#131)

When a tracker's *Security mailing list thread* body field records
two inbound Gmail threads — typically the original direct report
*and* a separate forwarder/relay thread that landed afterwards
(huntr.com bounty relay, GHSA forward, HackerOne forward,
ASF-security relay) — default reply drafts must target the
**primary reporter's** thread, not the forwarder's relay thread.
The relay thread is kept on the tracker for record-keeping and is
only used for the rarer back-channel relay message (e.g. "please
ask the external reporter to confirm a credit form").

Codifies the rule and detection signals (`via huntr.com`,
`ASF-relayed`, `relay`, `forwarded by`, `<provider>-class
duplicate`, etc.) in `tools/gmail/threading.md`, scopes the
existing `asf-relay.md` shape to the relay-thread-only case, and
adds one-paragraph pointers in the three drafting skills that
reply on an existing tracker's threads — `security-issue-sync`
(status updates), `security-cve-allocate` (CVE-allocated
notification), `security-issue-invalidate` (close-as-invalid
reply). No reshape of the existing line-per-reporter body-field
convention is needed.

Surfaced by airflow-s/airflow-s#351, where a primary report by
Vincent55 was followed by an Aymane Maguiti huntr.com bounty
relay; without this rule a future reply draft could land on the
relay thread, ASF-forwarder visible, instead of going back to the
primary reporter directly.

Generated-by: Claude Code (Opus 4.7)

Report URL: https://github.com/apache/airflow-steward/actions/runs/25703763161

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to