Repository navigation
chore: enforce the harness gates that pass, observe the others - #3
Merged
Merged
Conversation
Harness v0.1.3. Reported only: Code style, Dependency analysis.
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.
.harness.jsongoes from observe to enforce. Every gate that passes now blocks (static analysis, tests and architecture, dependency policy, audit, public surface, ratchet, the PHP API compatibility and secrets jobs). Still reported only, listed inobserved: Code style, Dependency analysis.Harness v0.1.3 (
observedsupport), workflow pinned to it. Same change as Pollora/hook#23.