Audit the remaining repositories for runner egress exposure #788
Labels
No labels
burndown-2026-06
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/infrastructure#788
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Four repositories were checked while investigating the pre-commit network
failures: deploy, sirens-echo, agentic-os, infrastructure. Roughly twenty were
not.
Every repository whose CI runs
runs-on: dockerand fetches from the networktakes the same DinD path. website, eco-app, ward, ward-mcp, cli-guard, atlas,
galaxy-gen, voice-corpus, steam-ops, eco-mods and the rest are unmeasured.
Scope
Per repository, record whether CI fetches from the network, whether it caches,
and whether it opts into the egress proxy. The MTU fix would cover all of them
at once, so this is mainly worth doing to size the problem and to catch
repositories that need neither.