docs(projects/_template): genericise remaining Airflow-specific residue#795
Merged
Merged
Conversation
The Step 6d template-genericity audit (run during /magpie-setup upgrade in an adopter repo) flagged a few _template configs carrying unmarked Airflow-specific values as defaults, unlike the many correctly annotated with Example: / e.g. / (filled example). - pr-management-quick-merge-config.md: the default deny_globs listed literal airflow-core/... and task-sdk/... paths; replace with a <core-src-path>/** placeholder plus a commented Airflow example. - security-tracker-stats.md: genericise the airflow-s/airflow-s adopter reference and drop "Airflow" from the ASF-default / non-ASF overlay prose. - cve-allocation-config.md: genericise the airflow-s/airflow-s reference-adopter mention to <org>/<repo>. Correctly-marked example values elsewhere are left as-is. Generated-by: Claude Code (Claude Opus 4.8 (1M context))
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
/magpie-setup upgradeStep 6d template-genericity audit (run in anadopter repo) flagged a few
projects/_template/configs that still carryunmarked Airflow-specific values as defaults — as opposed to the many
correctly annotated with
Example:/e.g./(filled example), whichare fine.
Changes
pr-management-quick-merge-config.md— the defaultdeny_globsblock listed literal
airflow-core/...+task-sdk/...paths. Replacedwith a
<core-src-path>/**placeholder plus a commented Airflow-monorepoexample, so a fresh adopter starts from a project-agnostic scaffold
rather than inheriting Airflow-shaped globs.
security-tracker-stats.md— genericised theairflow-s/airflow-sadopter reference to
<org>/<repo>and dropped "Airflow" from theASF-default / non-ASF overlay prose.
cve-allocation-config.md— genericised theairflow-s/airflow-sreference-adopter mention to
<org>/<repo>.Correctly-marked example values elsewhere (
release-management-config,mentoring-*,onboarding-concierge,committer-onboarding,pr-management-config,pr-management-code-review-criteria) are left as-is.Surfaced by the Step 6d audit; docs-only,
prekgreen.