The GitHub Actions job "prek" on 
airflow-steward.git/fix/extract-airflow-defaults-pr-management has failed.
Run started by GitHub user andreahlert (triggered by potiuk).

Head commit for run:
94762098e3e47eb965d43f5d077d72b0591f70ed / André Ahlert <[email protected]>
refactor(skills): extract Airflow-flavored defaults from PR-management skills 
into project-config templates

Extract all Apache-Airflow-specific defaults from the three
PR-management skills into the project-agnostic
`projects/_template/` configuration files:

**Templates filled with Airflow reference values:**
- `pr-management-config.md` — identifiers, labels, grace windows
- `pr-management-triage-comment-templates.md` — all 10+ comment
  bodies, AI footer, project URLs, communication channel
- `pr-management-triage-ci-check-map.md` — CI-check pattern →
  category + doc-URL mapping (12 categories)
- `pr-management-code-review-criteria.md` — repo-wide and per-area
  source files, security-model doc, backport pattern, section anchors

**Skills made fully project-agnostic:**
- `pr-management-triage/` — comment-templates, classify-and-act
  (real-CI patterns, static-check heuristic), workflow-approval,
  interaction-loop, prerequisites, rationale, actions, SKILL.md
- `pr-management-code-review/` — criteria (source-file table now
  references config), selectors, review-flow, adversarial, posting,
  SKILL.md
- `pr-management-stats/` — fetch (hybrid GraphQL query uses
  ``/`` variables), SKILL.md

Also updates `projects/_template/README.md` to reflect that skills
now read exclusively from `<project-config>/` with no baked-in
framework defaults.

The `check-placeholders` linter passes, confirming no hardcoded
project references remain in the skills.

Signed-off-by: André Ahlert <[email protected]>

Report URL: https://github.com/apache/airflow-steward/actions/runs/25349359481

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to