potiuk opened a new pull request, #283:
URL: https://github.com/apache/airflow-steward/pull/283
## Summary
Follow-up to #280, which added a `Step 6d` template-genericity check
on `/setup-steward upgrade` and fixed the first concrete instance
(`_template/pr-management-config.md`). This PR fixes the second one
the check would flag.
`projects/_template/pr-management-triage-ci-check-map.md` was a
byte-for-byte copy of one adopter's CI mapping. Anyone copying it as
a scaffold inherited:
- A title hardcoded to that project's name (no `<Project Name>`
placeholder).
- Every doc URL pointing at `apache/airflow/blob/main/contributing-
docs/...` paths that 404 for any other adopter.
- A `provider` pattern row tied to that project's plugin architecture.
## What changed
- Title becomes `# TODO: \`<Project Name>\` — ...` matching the
convention used in `project.md` / `canned-responses.md` / the
`pr-management-config.md` cleanup from #280.
- Every doc URL becomes a `<...-doc-url>` placeholder
(`<static-checks-doc-url>`, `<unit-tests-doc-url>`,
`<docs-building-doc-url>`, etc.). Adopters fill them in by hand —
one substitution per row.
- The `provider` row is dropped; its slot is replaced by a snippet
showing the row format so adopters can add their own subsystem
patterns above the catch-all.
- Pattern strings (`mypy-`, `ruff`, `helm`, `k8s`, `unit test`,
`pre-commit`, `prek`, etc.) stay — they're widely-used CI-check
naming conventions, useful as starting defaults.
- The `mypy-airflow-core` example in the Notes section becomes
`mypy-<sub-project>` (illustrates the same "more-specific above
broader" rule without naming a particular project).
## Test plan
- [x] prek passes (markdownlint, doctoc, typos, check-placeholders)
- [x] Step 6d audit on this file would now find nothing — scans
clean against the heuristics introduced in #280
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]
