Skip to content

ci: audit and minimize privileged issue-policy workflow permissions #490

Open

Description

@codeforester

Goal

Reduce the blast radius of the issue-branch policy workflow, which runs on pull_request_target.

Current evidence

The workflow does not check out or execute pull-request code, which avoids the classic privileged-PR execution pattern. It still grants actions: write and statuses: write so it can dispatch revalidation and publish statuses.

Scope

  • Determine whether self-dispatch can be replaced with a reusable workflow, workflow_run, or another lower-privilege design.
  • Remove any permission not required by the final implementation.
  • Preserve strict validation and quoting of all PR-derived values.
  • Add workflow security linting and a regression fixture proving that untrusted PR code is never checked out or executed.

Acceptance criteria

  • The workflow has the minimum required token permissions.
  • No pull_request_target job checks out or runs PR-provided code.
  • Branch-policy behavior and stale-commit repair remain covered by hosted checks.
  • The security model is documented for maintainers.

This is a v1.0 hardening item; it can follow the P0 publication controls if needed.

Activity

  1. added this to the v1.0.0 milestone on Oct 26, 2026
  2. self-assigned this
    on Oct 26, 2026
  3. added
    ciContinuous integration, tests, automation, or release workflows
    on Oct 26, 2026
  4. moved this to Backlog in base-clion Oct 26, 2026
  5. moved this from Backlog to In Progress in base-clion Oct 26, 2026
  6. moved this from In Progress to Ready in base-clion Oct 26, 2026
  7. codeforester commented on Oct 27, 2026

    @codeforester
    ContributorAuthor

    Implementation PR #493 adds a narrow trusted Dependabot exception to the issue-branch policy; human and fork-owned branches remain subject to the canonical issue-backed format.

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

Metadata

Metadata

Assignees

Labels

ciContinuous integration, tests, automation, or release workflows

Type

No type

Projects

  • Status
    Ready

Relationships

None yet

Development

No branches or pull requests

Issue actions