Skip to content

ci: harden workflow execution boundaries - #7

Merged
umutseve4 merged 1 commit into
mainfrom
quality/workflow-hardening-20260829
Sep 3, 2026
Merged

umutseve4 merged 1 commit into
mainfrom
quality/workflow-hardening-20260829

Conversation

@umutseve4

Copy link
Copy Markdown
Owner

Summary

  • pin GitHub Actions to immutable revisions and set explicit read-only defaults
  • add bounded timeouts and concurrency controls
  • constrain the write-enabled formatter to exact main, make no-change handling index-aware, and push explicitly to main

Reproduced defects

The current workflows use mutable action tags, have no timeout/concurrency controls, and the manual formatter can be dispatched from an arbitrary ref with repository-wide write permission and an ambiguous git push.

Scope

Only .github/workflows/ci.yml and .github/workflows/format.yml are changed. Runtime code, tests, dependencies, and generated reports are untouched.

Acceptance

  • PR-head ci quality job passes
  • formatter remains manual-only and its write-capable job is gated to refs/heads/main
  • independent QA confirms no blocking workflow regression

No merge is requested by this PR.

@umutseve4
umutseve4 merged commit 6170abf into main Sep 3, 2026
1 check passed
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