You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix Action Pinning Rule Requires a v-Prefixed Comment That Hub Release Tags Cannot Carry #1805 in GOVERNANCE.md "Workflow YAML Conventions", Action pinning bullet: state the trailing version comment as the referenced ref's release tag (# vX.Y.Z for an upstream action, the bare release tag such as # 2.0.672 for a hub task) rather than prescribing the v form. Bring WORKFLOW.md D9.1 ("a version comment") into agreement so the two canonical statements no longer disagree.
In the same edit, the second defect in the issue's comment: say what $/ denotes where the bullet exempts it. The tree settles the choice the comment offers: $/ is GitHub's self-repository syntax the hub's own tasks use (.github/workflows/*-task.yml, described in docs/reusable-workflows.md), so name it and what it resolves to rather than dropping it and naming only ./. Check WORKFLOW.md D9.1 and its trace paragraph, which also name $/, for the same gap.
Rebuild the generated skill distributions (scripts/build_dist.py) if any include region carries the edited text, run the full local gate set including spec/validate.py and the prose gate, and drive the pull request to develop with Closes on promotion: #1805.
Done looks like: a hub-task pin with a bare-tag comment reads as conforming under the rule text, the $/ exemption is intelligible to a downstream reader holding only that section, and the pull request is merged to develop.
External blockers
None known.
Internal dependencies
Step 3 depends on steps 1 and 2 landing in one change, since both edit the same bullet.
State
No branch, worktree, or pull request exists for this lane yet. Base the worktree on develop. The edited text is carried canonical content, so every carrier picks it up on its next resync.
The parked decision queue
None.
What the last round did
Nothing. This lane was created by an unattended picker from the open backlog.
Next steps, in priority order
GOVERNANCE.md"Workflow YAML Conventions", Action pinning bullet: state the trailing version comment as the referenced ref's release tag (# vX.Y.Zfor an upstream action, the bare release tag such as# 2.0.672for a hub task) rather than prescribing thevform. BringWORKFLOW.mdD9.1 ("a version comment") into agreement so the two canonical statements no longer disagree.$/denotes where the bullet exempts it. The tree settles the choice the comment offers:$/is GitHub's self-repository syntax the hub's own tasks use (.github/workflows/*-task.yml, described indocs/reusable-workflows.md), so name it and what it resolves to rather than dropping it and naming only./. CheckWORKFLOW.mdD9.1 and its trace paragraph, which also name$/, for the same gap.scripts/build_dist.py) if any include region carries the edited text, run the full local gate set includingspec/validate.pyand the prose gate, and drive the pull request to develop withCloses on promotion: #1805.Done looks like: a hub-task pin with a bare-tag comment reads as conforming under the rule text, the
$/exemption is intelligible to a downstream reader holding only that section, and the pull request is merged to develop.External blockers
None known.
Internal dependencies
Step 3 depends on steps 1 and 2 landing in one change, since both edit the same bullet.
State
No branch, worktree, or pull request exists for this lane yet. Base the worktree on
develop. The edited text is carried canonical content, so every carrier picks it up on its next resync.The parked decision queue
None.
What the last round did
Nothing. This lane was created by an unattended picker from the open backlog.
What not to repeat
Nothing yet.
New learnings
None yet.