Repository navigation
chore: adopt the Pollora harness in observe mode - #2
Merged
Merged
Conversation
Profile core, observe mode: every gate runs and reports, none blocks. The WordPress PHPStan extension is included once, through the harness preset.
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.
Applies
pollora-qa init --profile=core(harness v0.1.0, workflow pinned to v0.1.0). Observe mode: every gate runs and reports, none blocks. No runtime change: the harness is arequire-dev.api-surface.jsonrecords the public surface as it is today; from now on a change to it needs theapi-changeorbreakinglabel. The findings ofcomposer qaare in the job summary, to settle before switching to enforce.