Repository navigation
ci(quality): publish the SIG profile on full-scope runs, opt-in blocking for gate 122 - #872
Merged
Merged
Conversation
…ing for gate 122 Gate 122 writes the SIG maintainability profile on a run with no delta base, which is the daily drift sweep's dispatch. The Hydra Gates job now points it at RUNNER_TEMP, adds the markdown table to the job summary and uploads sig-profile.json and sig-profile.md as the sig-profile artifact. hydra-gates-sig-blocking (default false) is the named opt-in that makes the gate's ratchet block for a repo.
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.
What
Two additions to the Hydra Gates job in
quality.yml, for gate 122 (sig-maintainability):RUNNER_TEMP/sig-profile. The job adds its markdown table to the job summary and uploadssig-profile.jsonandsig-profile.mdas thesig-profileartifact. When no profile was written, the summary says so instead of staying silent.hydra-gates-sig-blocking(default false), is the named opt-in that makes the gate's ratchet block for a repo. It is passed as an explicit'1'/'0', likehydra-gates-e2e-anchor-blocking.Why
The daily fleet drift sweep dispatches every app's Code Quality on
development. A dispatch has no diff, so the gates run at full scope, and that is when gate 122 measures the whole app. This gives a nightly SIG profile per app without a new workflow.Depends on
The gate itself, #871 (gate 122). Merged before it, this changes nothing: the variables are unused and the publish step reports that no profile was written.
Verified
The workflow parses as YAML (
python3 -c "import yaml; yaml.safe_load(...)", exit 0). Not run in CI from this branch: the publish step only runs on a full-scope dispatch of an app's workflow.🤖 Generated with Claude Code