Skip to content

ci: restrict perf workflow token permissions#33

Closed
saagpatel wants to merge 1 commit into
mainfrom
codex/security-workflow-permissions-20260518
Closed

ci: restrict perf workflow token permissions#33
saagpatel wants to merge 1 commit into
mainfrom
codex/security-workflow-permissions-20260518

Conversation

@saagpatel
Copy link
Copy Markdown
Owner

What

  • Add explicit read-only workflow permissions to the perf-enforced workflow.

Why

  • Clears the open code-scanning workflow-permissions alert by avoiding the default write-capable token posture.

How

  • Set top-level permissions: contents: read; existing job-level read permissions remain unchanged.

Testing

  • Commands run: python3 YAML parse for .github/workflows/perf-enforced.yml; GitHub compare check.
  • Results: Workflow YAML parsed successfully; remote branch diff contains only .github/workflows/perf-enforced.yml.

Performance impact

  • Bundle delta: N/A
  • Build time delta: N/A
  • Lighthouse delta: N/A
  • API latency delta: N/A
  • DB query delta: N/A

Risk / Notes

  • Low risk; this workflow only needs repository read access for checkout and local checks.

Screenshots (UI only)

  • N/A

Lockfile rationale (if lockfile changed)

  • N/A

Baseline governance (if .perf-baselines changed)

  • perf-baseline-update label applied: N/A
  • Reviewer signoff: N/A
  • Rollback note: Revert this workflow-only commit if a permission regression appears.

@saagpatel
Copy link
Copy Markdown
Owner Author

Closing and republishing this same one-file workflow permission fix under the repository-required branch naming pattern so CI can pass cleanly.

@saagpatel saagpatel closed this May 18, 2026
@saagpatel saagpatel deleted the codex/security-workflow-permissions-20260518 branch May 18, 2026 07:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant