potiuk opened a new pull request, #324: URL: https://github.com/apache/airflow-steward/pull/324
## Summary - Adds three issue templates (`bug_report.yml`, `change_proposal.yml`, `config.yml`) and one PR template (`PULL_REQUEST_TEMPLATE.md`) that operationalise the guidance landed in CONTRIBUTING.md (#323). - The `change_proposal.yml` template is intent-first by design — required fields are *what* + *why* + which layer; *how* is explicitly out of scope at the issue stage and is left to the agentic loop on the eventual PR. - The PR template carries the `## Summary` + `## Test plan` shape documented in CONTRIBUTING.md, plus a Type-of-change checklist scoped to the framework's layer map and an explicit RFC-AI-0004 compliance checklist (six principles → six checkboxes). - `config.yml` disables blank issues, routes open-ended questions to Discussions, and routes adopter security vulnerabilities to the adopter project's `security@` list per ASF policy (not here). ## Type of change - [x] Documentation (`docs/`, `README.md`, `CONTRIBUTING.md`) — issue / PR template scaffolding - [x] CI / dev loop (`prek`, workflows, validators) — doctoc exclude tweak ## Test plan - [x] `prek run --files .pre-commit-config.yaml .github/ISSUE_TEMPLATE/*.yml .github/PULL_REQUEST_TEMPLATE.md` passes - [x] Verified the PR template is no longer touched by doctoc after adding it to the exclude list — `head` of the file starts at the SPDX header, no TOC injected - [x] Issue templates are GitHub Issue Forms YAML — render shape can be verified once merged via the *New issue* flow ## Companion change in `.pre-commit-config.yaml` GitHub pre-populates a new PR description with the template verbatim, so a doctoc-generated TOC becomes per-PR noise that the contributor has to delete by hand. Added `\.github/PULL_REQUEST_TEMPLATE\.md` to the doctoc exclude pattern. ## Linked issues Follows from #323 (CONTRIBUTING.md rewrite — landed). 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
