A reusable workflow call was a string the compiler refused wholesale. It is now
addressed: a local call names a path in the same commit, a remote one names a
repository, a path and a revision. A call naming no workflow file, or a
repository with no revision, is refused when it is read rather than when
something tries to fetch it.
The compiler still refuses to expand either — expanding belongs to whoever
decides what runs — but it now says which kind it is refusing. That is the
difference between needing the other files of the commit already in hand and
needing a fetch from another repository, which is exactly the fork the control
plane has to take next.
A reusable workflow call was a string the compiler refused wholesale. It is now
addressed: a local call names a path in the same commit, a remote one names a
repository, a path and a revision. A call naming no workflow file, or a
repository with no revision, is refused when it is read rather than when
something tries to fetch it.
The compiler still refuses to expand either — expanding belongs to whoever
decides what runs — but it now says which kind it is refusing. That is the
difference between needing the other files of the commit already in hand and
needing a fetch from another repository, which is exactly the fork the control
plane has to take next.
## Verification
`cargo fmt --check`, `cargo clippy --workspace --all-targets --all-features -- -D warnings`,
`cargo test --workspace --all-targets --all-features`, `check-architecture.sh`,
`check-rust-loc.sh`.
A reusable workflow call was a string the compiler refused wholesale. It is now
addressed: a local call names a path in the same commit, a remote one names a
repository, a path and a revision, and a call naming no workflow file or no
revision is refused when it is read.
The compiler still refuses to expand either — that belongs to the control plane
— but it now says which kind it is refusing, which is the difference between
needing the commit's other files and needing a fetch.
A workflow that can be called says so with on: workflow_call, and the reader
refused it as an event nobody acts on — which made every callable workflow
unreadable, and reusable calls unusable in practice.
It now reads as what it is: being callable is not something that happened, so it
declares no trigger and fires on nothing.
day01
merged commit 8158ff0faf into %!s()2026-08-06 09:19:48 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
A reusable workflow call was a string the compiler refused wholesale. It is now
addressed: a local call names a path in the same commit, a remote one names a
repository, a path and a revision. A call naming no workflow file, or a
repository with no revision, is refused when it is read rather than when
something tries to fetch it.
The compiler still refuses to expand either — expanding belongs to whoever
decides what runs — but it now says which kind it is refusing. That is the
difference between needing the other files of the commit already in hand and
needing a fetch from another repository, which is exactly the fork the control
plane has to take next.
Verification
cargo fmt --check,cargo clippy --workspace --all-targets --all-features -- -D warnings,cargo test --workspace --all-targets --all-features,check-architecture.sh,check-rust-loc.sh.