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

   ## Summary
   
   Adds a defensive hygiene step to `/setup-steward upgrade` (Step 6d)
   that scans every file under `projects/_template/` for adopter-
   specific data — project names in H1s, hardcoded URLs, real
   committer-team slugs, calibration prose tied to one project. Surfaces
   findings as ⚠ rows in the upgrade summary so the operator can file a
   tracking issue upstream. Purely advisory; never modifies the
   snapshot, never auto-fixes.
   
   Also fixes the first concrete instance the check would flag:
   `projects/_template/pr-management-config.md` was a byte-for-byte copy
   of one adopter's config, so anyone copying it as a template inherited
   that project's name, committer-team slug, and traffic-profile prose.
   
   ## What changed
   
   - **`projects/_template/pr-management-config.md`** — title becomes
     `# TODO: \`<Project Name>\` — ...` (matching the convention already
     used in `project.md` and `canned-responses.md`). `committers_team`
     becomes `<github-org>/<committers-team-slug>` with an `Example: …`
     annotation. Grace-window prose generalised to "sized for ~50–100
     open PRs / sweep every 1–2 days; scale up for lower traffic".
     Suggested label strings kept — readable English that works for
     most projects.
   - **`.claude/skills/setup-steward/upgrade.md`** — new Step 6d
     ("Audit framework template genericity") + a corresponding
     `Framework templates:` row in the Step 8 output template.
     Heuristic, per-file, runs on every upgrade.
   
   ## Why first of a series
   
   `projects/_template/pr-management-triage-ci-check-map.md` has the
   same problem — hardcoded `apache/airflow/blob/main/contributing-
   docs/...` URLs and check-name patterns tied to one project's CI.
   Follow-up PR.
   
   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