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

   Bumps the apache-steward framework snapshot pin from b9e1967 to b19ac36
   (4 commits), re-syncs the committed `setup-steward` skill to the new
   snapshot, drops the per-file SPDX header we previously prepended on top
   of every framework skill file (the snapshot ships its own inline
   SPDX-License-Identifier inside the body), and excludes
   `.github/skills/setup-steward/` from the agentic-markdown insert-license
   prek hook so the header is not auto-re-added on subsequent commits.
   
   Also closes two `.gitignore` gaps surfaced by `/setup-steward verify`:
   
   - `/.claude/settings.local.json` — per-machine sandbox-allowlist file
     written by `setup-isolated-setup-install`'s helper (content is
     machine-specific absolute paths; must never be committed).
   - `/.claude/skills/issue-*` — Pattern-B mirror of the existing
     `/.github/skills/issue-*` entry, required for symmetry so a future
     `/setup-steward adopt` with the `issue` family does not stage symlinks.
   
   No new opt-in families wired (still `pr-management-*` only). Framework
   brought new skills behind opt-in that this PR does **not** turn on:
   `issue-*` (5), `security-*` (8), `contributor-nomination`, `write-skill`.
   
   ## Test plan
   
   - [x] `/setup-steward verify` reports ✓ on all checks
   - [x] `prek run --files <all 10 changed>` passes
   - [x] `prek run insert-license --files .github/skills/setup-steward/*.md`
         reports `(no files to check)` (exclusion takes effect)
   - [ ] CI passes on the PR
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Code (Opus 4.7)
   
   Generated-by: Claude Code (Opus 4.7) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)


-- 
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