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
The .github-private repo has codified a rule in its AGENTS.md and enforced it via a dev-lead prompt guardrail (part C, #1254) plus a CI guard (part A, #1253). This issue promotes the canonical org-wide standard so it applies to all consumer repos.
Rule to add
Under standards/ci-standards.md → "Reusable workflow versioning — the stable channel", add a subsection "Caller-stub input forwarding across channel pins":
A thin caller stub pins its first-party reusable at a moving channel tag (e.g. …@dev-lead/v1-stable), which resolves to a specific commit. The stub may only forward (with:) inputs that the reusable at that pinned commit declares under workflow_call.inputs. Forwarding an input the pinned channel does not yet declare is a channel-skew defect: the reusable call fails at runtime with an "unexpected input" error even though every ref looks valid.
Never add or modify a with: forward on a channel-pinned caller stub to pass an input the pinned channel does not yet declare.
Sequencing for a new workflow_call input (in order):
Land the input in the reusable's workflow_call.inputs on main.
Promote the pinned channel to a commit that declares it (cut-release.sh <agent> <version> --channel <name>).
Only then teach the stub to forward it with with:.
Acceptance
standards/ci-standards.md updated with the subsection above, and consumer repos defer to it.
Activity
don-petry commentedon Oct 21, 2026
Closing after the 2026-10-21 backlog triage.
Why: Rule codified in ci-standards.md.
Evidence: standards/ci-standards.md L241 'Caller-stub input forwarding across channel pins'
Reopen if this still reproduces on main.