Repository navigation
Run explicit fork hygiene on isolated owned capacity - #10
Merged
Merged
Conversation
krystophny
marked this pull request as ready for review
October 21, 2026 17:17
This was referenced Oct 21, 2026
This was referenced Oct 21, 2026
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.
Explicit fork validation in the shared hygiene gate for our repositories now runs on isolated owned Ubuntu capacity. Ordinary PR checks still skip before runner assignment; reviewed mergequeue checks retain the owned light runner and the same identity, blob and secret checks.
Validation: existing shared-gate tests and actionlint passed. The isolated Linux sudo-apt pilot is held during the current runner-host connectivity outage; no rollout completion is claimed. Immutable consumer pins will be updated only after this gate lands.
Chris&AI