potiuk opened a new pull request, #289:
URL: https://github.com/apache/airflow-steward/pull/289
## Summary
Same cleanup pattern as #280 / #283 — flagged by Step 6d audit
on a fresh upgrade — and mirrors the slim shape apache/airflow#67488
just adopted for its real override: the framework's
`comment-templates.md` ships default bodies for every triage
template, and this template file should provide only the
project-specific values the framework needs to render them.
The framework's `_template/pr-management-triage-comment-templates.md`
was seeded from one adopter's full override — title hardcoded,
URL table populated with `apache/airflow/blob/main/contributing-docs/...`
paths as the "template values", AI-attribution footer body with
"Apache Airflow maintainer" baked in, and 13 template-body
sections copied from the framework default.
## What changed
- Title → `# TODO: \`<Project Name>\` — ...`.
- URL table values → `<docs-base-url>/<doc-path>` placeholder
form, adopter substitutes one per row.
- AI-attribution footer body uses `<PROJECT>` and
`<two_stage_triage_rationale_url>` placeholders that resolve
from the URL table.
- Quality-criteria marker string section stays — framework
constant, identical across all adopters.
- The 13 template-body sections are removed. The framework's
comment-templates.md is the source of truth for default
bodies; adopters override only ones that genuinely diverge.
A new `Template body overrides` section explains the
contract + the workflow-variant config path
(`confirmation_handback_mode` from #286) so adopters know to
configure rather than body-override for the variants the
framework already supports.
This mirrors the slim shape apache/airflow#67488 just
established for that project's real override (320 → 196 lines).
Adopters starting fresh from this template now arrive at the
slim shape directly.
## Test plan
- [x] prek passes
- [x] Step 6d audit on this file would now find nothing
Generated-by: Claude (Opus 4.7)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
