ci: enable the Hydra mechanical gate tier — it has never run in this repo - #2335
Merged
Conversation
`enable-hydra-gates` defaults to false, so `quality / Hydra Gates` has been SKIPPED on every run this repository has ever had. A skipped job is neither a pass nor a failure in the Quality Report rollup, so the gate tier's absence has been indistinguishable from its success — the gates have never rendered a verdict here. Pinned to v1.0.1 rather than `main` so a change to the gate package cannot move this repo's verdict without a commit here, and because v1.0.1 is the pin openbuild already runs — the one live-verified reference result the fleet has, which makes this repo's first result directly comparable. `enable-axe` is deliberately left off: it produces the report gate-33 consumes, and a vanilla Nextcloud already carries serious/critical axe violations, so enabling it here would mix 'this repo has a defect' with 'core does'.
Contributor
Quality Report — ConductionNL/openregister @
|
| Check | PHP | Vue | Security | License | Tests |
|---|---|---|---|---|---|
| lint | ✅ | ||||
| phpcs | ✅ | ||||
| phpmd | ✅ | ||||
| psalm | ✅ | ||||
| phpstan | ✅ | ||||
| phpmetrics | ✅ | ||||
| eslint | ✅ | ||||
| stylelint | ✅ | ||||
| build | ✅ | ||||
| composer | ✅ | ✅ 173/173 | |||
| npm | ✅ | ✅ 713/713 | |||
| PHPUnit | ✅ | ||||
| Newman | ✅ | ||||
| Playwright | ✅ |
Quality workflow — 2026-08-04 13:34 UTC
Download the full PDF report from the workflow artifacts.
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.
What this turns on
quality / Hydra Gates— the mechanical gate tier fromconduction/hydra-gates— has never executed in this repository.enable-hydra-gatesdefaults tofalsein the shared workflow, and this caller never set it. So the job has been SKIPPED on every run openregister has ever had. A skipped job is neither a pass nor a failure in the Quality Report rollup, which means the gate tier's absence has been indistinguishable from its success. That is the whole reason for switching it on rather than assuming the gates were already covering this repo.Why this is safe to switch on mid-flight
The gates are diff-scoped per ADR-020: each one inspects only the files this PR changes, so inherited debt on untouched trees cannot block unrelated work. That claim is the thing this PR measures — the run on this PR is itself the evidence.
The dependency that does not delete the job
hydra-gatesdeclaresneeds: [..., playwright], andneeds:impliessuccess()— which would make the whole job vanish for every repo that has the gates on and Playwright off, with no red, no skip and no trace. The shared workflow guards against exactly that withif: ${{ inputs.enable-hydra-gates && !cancelled() }}, which suppresses the implicitsuccess().Verified live rather than assumed: on openbuild run 30911188960,
E2E Tests (Playwright)was skipped andHydra Gatesstill ran to success. This repo hasenable-playwright: trueanyway, so the edge is satisfied here regardless.The pin
hydra-gates-ref: v1.0.1, notmain, so a change to the gate package cannot move this repository's verdict without a commit here to move the pin.v1.0.1 is also the pin openbuild already runs, which makes this repo's first result directly comparable to the only live-verified reference the fleet has. Measured there on a PR with a real 2-file diff:
v1.1.0exists. Moving to it is a separate, measurable change, not a side effect of this one.What is deliberately not enabled
enable-axestays off. It is the input that producestests/axe/report.json, the file gate-33 consumes; without it gate-33 reports SKIPPED, as it has in every repo in the fleet since it was written.Measured against a vanilla Nextcloud with no app installed, core's own pages already carry serious/critical axe violations. Enabling it in the same change as the gate tier would mix "this repo has an accessibility defect" with "Nextcloud core does". Separate change, separate verdict.
Expected outcome
Red is an acceptable and possibly correct result. The point is to find out what this repository actually does under the gates, not to produce a green tick. No gate has been weakened, baselined or suppressed to get there.