The GitHub Actions job "prek" on airflow-steward.git/contribitor-onboarding has 
failed.
Run started by GitHub user justinmclean (triggered by justinmclean).

Head commit for run:
4c92488622f59d31e6033fa6ef9af7c7df1cd445 / Justin McLean 
<[email protected]>
fix(skills): clear validator pytest failure + SOFT warnings

Address the skill-validator findings surfaced by the pytest run on
this branch, plus two markdownlint MD040 errors the lint hook
surfaced on the touched committer-onboarding SKILL.md:

- committer-onboarding: add the standard Pattern 4 injection-guard
  callout. The skill reads the <vote-thread> from the mailing-list
  archive, candidate-supplied identity fields (name, email, desired
  Apache ID), and ICLA / Whimsy roster data; the callout names those
  surfaces explicitly. Golden rule 3 already reinforced the same
  principle; this adds the validator-recognised block. (HARD
  violation; was failing the pytest gate.)
- committer-onboarding: tag two existing untagged fenced output
  blocks (Step 0 output, Step 3 completion summary) as `text` so
  markdownlint MD040 stops flagging them on touch.
- security-issue-sync: add `--limit 100` to the milestone-siblings
  `gh issue list` count (was unbounded; silently capped at 30 on
  large repos).
- security-issue-triage: add `--limit 100` to the reviewed-by
  `gh pr list` search (same reason).
- setup-isolated-setup-doctor: move the docs/setup/
  sandbox-troubleshooting.md reference out of the frontmatter
  description into the body, so the matching-layer description stays
  tight and the criteria-source SOFT advisory clears. The body
  still documents the link extensively.
- committer-onboarding eval fixtures: append the missing trailing
  newline to 5 expected.json files.

Verified: `skill-validate --strict` reports OK (no violations);
`skill-validator` pytest suite is green; markdownlint passes.

Generated-by: Claude Code (Opus 4.7)

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

With regards,
GitHub Actions via GitBox


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

Reply via email to