Repository navigation
ci: harden workflow execution boundaries - #7
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
main, make no-change handling index-aware, and push explicitly tomainReproduced 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.ymland.github/workflows/format.ymlare changed. Runtime code, tests, dependencies, and generated reports are untouched.Acceptance
ciquality job passesrefs/heads/mainNo merge is requested by this PR.