Skip to content

spike lane: enforce contents: read for spike/* workflows (ruleset or required check) #63

Open

Description

@djbclark

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.

🤖 Generated with Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions