Skip to content

[v3-2-test] PR triage: drop failing job names from violations bullets (#67322)#67421

Merged
potiuk merged 1 commit into
apache:v3-2-testfrom
potiuk:cherry-pick-67322-v3-2-test
May 24, 2026
Merged

[v3-2-test] PR triage: drop failing job names from violations bullets (#67322)#67421
potiuk merged 1 commit into
apache:v3-2-testfrom
potiuk:cherry-pick-67322-v3-2-test

Conversation

@potiuk

@potiuk potiuk commented May 24, 2026

Copy link
Copy Markdown
Member

Cherry-pick of #67322 onto v3-2-test (now possible after #67420 brought the apache-steward framework adoption to this branch).

Pins `` bullets in PR-triage comments to the bare-category form on v3-2-test as well:

```

  • . See docs.
    ```

— no per-failing-job-name listing under each category.

Discussed on the dev list — "RE: Re: [DISCUSS] PR auto-triage recent stats (how do we do more reviews)".


Was generative AI tooling used to co-author this PR?
  • Yes — Claude Code (Opus 4.7)

Generated-by: Claude Code (Opus 4.7) following the guidelines

The contributor-facing triage comments currently enumerate every
failing job name underneath each category (e.g. five Kubernetes
test variants plus "(+1 more)"). The same job names are already
visible in GitHub's Checks tab; repeating them in the comment
adds noise and pushes the message past the size where
contributors actually read it.

Pin the bullet to the bare-category form via the override
file. Per-category remediation snippets the framework default
may add (e.g. inline "Run prek run ..." steps) are dropped too;
the linked doc has them. Short single-clause inline payloads
(unresolved-thread count, the existing "Multiple flagged PRs"
line in `close`) remain permitted — the rule applies to
multi-item job-name lists, not to all auxiliary text.

The rest of the triage comment — link to the quality criteria,
per-category doc URLs, "what to do next" / no-rush line, AI-
attribution footer, two-stage-process link — is untouched.
@potiuk potiuk added this to the Airflow 3.2.2 milestone May 24, 2026
@potiuk potiuk merged commit 9d3a32a into apache:v3-2-test May 24, 2026
62 checks passed
@potiuk potiuk deleted the cherry-pick-67322-v3-2-test branch May 24, 2026 15:47
vatsrahul1001 pushed a commit that referenced this pull request May 25, 2026
The contributor-facing triage comments currently enumerate every
failing job name underneath each category (e.g. five Kubernetes
test variants plus "(+1 more)"). The same job names are already
visible in GitHub's Checks tab; repeating them in the comment
adds noise and pushes the message past the size where
contributors actually read it.

Pin the bullet to the bare-category form via the override
file. Per-category remediation snippets the framework default
may add (e.g. inline "Run prek run ..." steps) are dropped too;
the linked doc has them. Short single-clause inline payloads
(unresolved-thread count, the existing "Multiple flagged PRs"
line in `close`) remain permitted — the rule applies to
multi-item job-name lists, not to all auxiliary text.

The rest of the triage comment — link to the quality criteria,
per-category doc URLs, "what to do next" / no-rush line, AI-
attribution footer, two-stage-process link — is untouched.
vatsrahul1001 pushed a commit that referenced this pull request May 25, 2026
The contributor-facing triage comments currently enumerate every
failing job name underneath each category (e.g. five Kubernetes
test variants plus "(+1 more)"). The same job names are already
visible in GitHub's Checks tab; repeating them in the comment
adds noise and pushes the message past the size where
contributors actually read it.

Pin the bullet to the bare-category form via the override
file. Per-category remediation snippets the framework default
may add (e.g. inline "Run prek run ..." steps) are dropped too;
the linked doc has them. Short single-clause inline payloads
(unresolved-thread count, the existing "Multiple flagged PRs"
line in `close`) remain permitted — the rule applies to
multi-item job-name lists, not to all auxiliary text.

The rest of the triage comment — link to the quality criteria,
per-category doc URLs, "what to do next" / no-rush line, AI-
attribution footer, two-stage-process link — is untouched.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant