gate merges on one check and isolate the release build - #46
Merged
Conversation
ci-ok aggregates every job of a CI run: it fails on any failure or cancellation and passes when everything triggered passed or was skipped. Branch protection requires only this one context, so conditional jobs never need enumerating in rulesets. The release job refuses to run outside this repository and builds without the Actions cache: cache entries are writable from any PR branch, so restoring one would let poisoned content reach the publishing build.
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
1 participant
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.
Repo-hardening groundwork:
ci-okaggregate gate: fails on any failed/cancelled job in the run, passes when everything triggered passed or was skipped. Becomes the single required status check in the upcoming main ruleset — conditional future jobs stay covered without enumerating contexts.github.repository == 'GaijinEntertainment/go-gerrit-mcp'(no fork/mirror execution) and runs withsetup-gocache disabled — the Actions cache is writable from any PR branch, so restoring it in the publishing build is a poisoning vector.Rulesets (main protection + v* tag immutability) follow via API once this lands.