potiuk opened a new pull request, #288:
URL: https://github.com/apache/airflow-steward/pull/288

   ## Summary
   
   Same cleanup pattern as #280 / #283 — flagged by Step 6d audit
   on a fresh upgrade.
   
   The template was seeded from one adopter's review-criteria
   map: title hardcoded, per-area rows pointing at that project's
   subtree structure (`registry/`, `dev/`, `providers/<name>/`,
   `providers/elasticsearch/`, `providers/opensearch/`), backport-
   branch pattern tied to that project's release-train naming
   (`v\d+-\d+-test`), and 14 section-anchor URLs all pointing at
   one project's review-instructions doc.
   
   ## What changed
   
   - Title → `# TODO: \`<Project Name>\` — ...`.
   - Repo-wide source files (`.github/instructions/code-review.instructions.md`,
     `AGENTS.md`) stay since those are standard locations; cell
     notes now say "reuse if your project already uses it".
   - Per-area table becomes three illustrative `<subtree>` /
     `<plugins-dir>` / `<specific-plugin>` rows that adopters
     replace with their real tree structure.
   - Security-model calibration doc path → `<security-model-doc-path>`
     placeholder with "Example: airflow-core/..." annotation.
   - Backport-branch pattern → `<your-backport-branch-regex>`
     placeholder with the airflow regex as an example.
   - Section anchors → `<docs-base-url>/<doc-path>#<anchor>`
     placeholders. The three universal Apache-license-policy
     URLs (legal/src-headers.html, legal/resolved.html,
     legal/apply-license.html) stay as-is — they're
     framework-host-org links, not adopter-specific.
   
   ## 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]

Reply via email to