Repository navigation
[dev]: generated bug forms, CI version check and rollout for profiles #780
Description
Your feedback for the existing codebase
Follow-up to the project profiles of ADR-0040 (#779). Three parts of the issue intake plan remain after the profiles reach the org-routing block.
Acceptance criteria:
- Generated bug forms: for a profiled repository whose report fields justify a form, generate the repository bug form from the profile. Any file in a repository's
.github/ISSUE_TEMPLATE/hides every organization form, so a repository without local forms (z-shell/zpmod today) must receive the whole organization set plusconfig.yml, with each blob recorded inknowledge/domains/governance/data/template-exceptions.ymlso the community health audit keeps working. Decide the generator's language first:org-routing.pyreads JSON only, and the Org Routing workflow installs no YAML library. - CI version check:
org-routing.py checkcompares a profile'szsh.testedwith the versions the repository's workflows install. The four profiled repositories select Zsh three ways: amatrix.zshlist (zi), amatrix.versionlist with apatch-setinclude (zpmod), and aZSH_VERSIONenvironment value on a source build (F-Sy-H); zsh-lint pins oneversion:input. - Downstream delivery: z-shell/zi, z-shell/zsh-lint, z-shell/zpmod and z-shell/F-Sy-H each repin the Org Routing caller to a
maincommit that carries their profile, regenerate their block withorg-routing.py apply, and drop repository-owned text the section now duplicates, one reviewed pull request per repository.
Contact Details
Not applicable: filed by a maintainer.
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
fix(governance): read workflow Zsh versions by structure
refactor(governance): end a workflow key with a lookahead
feat(governance): check profile Zsh versions against CI (#782)
ci: repin org routing and add the reporting-issues section (#605)
fix(governance): drop the space inside the reporting heading span (#783)
ci: repin org routing and add the reporting-issues section (#155)
ci: repin org routing and add the reporting-issues section (#200)
ci: repin org routing and add the reporting-issues section (#633)
ci: repin org routing to the reporting heading fix (#606)
ss-o commentedon Oct 9, 2026
Done. Each acceptance item:
CI version check: feat(governance): check profile Zsh versions against CI #782 (23cd754).
org-routing.py checkfails when a profile'szsh.testeddiffers from the literal Zsh versions in the repository's workflows. It reads thezsh,zsh-version,zsh_versionandZSH_VERSIONkeys anywhere, andversiononly in a matrix or a setup-zsh step'swith:. It skipsrun: |bodies, and comments never end a list.Generated bug forms: not planned, by maintainer decision, recorded as ADR-0040 point 6. Any local form hides every organization form, so a profiled form would make each repository own and audit the whole form set. Agents, the main filing path, already get the extra headings from the generated
Reporting issuessection.Downstream delivery: every profiled repository pins Org Routing
2c5906fand carries the regenerated block. On eachmain,checkreports current, including the Zsh version comparison:No repository-owned text duplicated the section, so nothing was dropped.
Fix found during the rollout: z-shell/zpmod's markdownlint (MD038) rejected the generated "
`### `heading" span, so fix(governance): drop the space inside the reporting heading span #783 (2c5906f) removed the trailing space. zsh-lint was repinned to it in feat(review): require repository review-skill readiness #606, and all four blocks now match.ADR-0040 stays PROPOSED until the maintainer accepts it.
docs(governance): accept project profiles for issue intake (#784)
feat(governance): link the profile and ADR-0040 from the reporting se…
ci: repin org routing to link the project profile (#607)
ci: repin org routing to link the project profile (#156)
ci: repin org routing to link the project profile (#201)
ci: repin org routing to link the project profile (#634)