potiuk opened a new pull request, #44: URL: https://github.com/apache/airflow-steward/pull/44
## Summary Rebase + extend [#30](https://github.com/apache/airflow-steward/pull/30) (by @andreahlert). The original PR had drifted out of mergeability and didn't yet cover the `pr-management-*` skill family (lifted in #33, renamed in #35). Two commits: 1. **`docs: enable markdownlint MD040 and tag all fenced code blocks`** — @andreahlert's original commit, rebased onto current `main`. Git's similarity-detection followed the file renames (#31, #35) and moves (#36) cleanly — no conflicts. 2. **`docs: extend MD040 tagging to skills added since #30`** — 20 newly-untagged fences across the 3 `pr-management-*` skills. Same convention as #30 (most → `text`; markdown-link / list-item examples → `markdown`). ## Combined diff | Family | Files | Fences | New tags | |---|---|---|---| | `apache-steward` framework (commit 1, rebased from #30) | 19 | 64 | mostly `text`, a few `html` / `markdown` / `yaml` | | `pr-management-*` skills (commit 2, new) | 9 | 20 | mostly `text`, two `markdown` | `.markdownlint.json` flips `MD040: false → true` (commit 1). After both commits land, `prek run --all-files` reports zero MD040 violations across the tree. ## Test plan - [x] `git rebase origin/main` of #30's commit produced zero conflicts - [x] `prek run --all-files` clean (markdownlint, typos, doctoc, check-placeholders) - [x] `markdownlint-cli2 "**/*.md" "#node_modules" "#.git"` — zero violations - [x] Each new tag picked from #30's vocabulary (`text` for mockups + plain output, `markdown` for markdown-link / list-item examples) - [ ] Reviewer eyeballs the 20 new tag choices for any case that should be a more specific language than `text` - [ ] CI link-check (lychee) passes ## Attribution Original commit `f01eeea` is by @andreahlert (preserved verbatim through the rebase). Closes #30 once this lands. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
