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
{{ message }}
Repository navigation
spike lane: enforce contents: read for spike/* workflows (ruleset or required check) #63
Follow-up from the PR 62 review (adversary round 2, finding 5), not done in #62.
AGENTS.md standing rule 3 now has a spike lane: unmerged spike/* branches whose workflows get GitHub contents: read only. That limit is only a docs rule today. Nothing on GitHub stops a spike/* branch from pushing a workflow that asks for more (for example contents: write, id-token: write, packages: write, or secrets).
Proposed: a repository ruleset (or a required check) that refuses a spike/* push or PR whose workflow files ask for any permission beyond contents: read, or that use secrets.
Done when: a spike/* branch that adds a workflow with permissions: contents: write is refused or fails a required check, and one with contents: read passes.
Activity