GH Actions: few tweaks #115
Merged
Conversation
This file contains 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
As the `korelstar/xmllint-problem-matcher` repo now has a long-running `v1` branch, this update which was included in PR 114 is no longer needed (and would necessitate more frequent updates if it would remain). Ref: * korelstar/xmllint-problem-matcher 7
If there is a ruleset error, the `cs2pr` action doesn't receive an `xml` report and exits with a `0` error code, even though the PHPCS run failed (though not on CS errors, but on a ruleset error). This changes the GH Actions workflow to allow for that situation and still fail the build in that case.
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.
GH Actions/basics: revert to xmllint-problem-matcher v1
As the
korelstar/xmllint-problem-matcherrepo now has a long-runningv1branch, this update which was included in PR #114 is no longer needed (and would necessitate more frequent updates if it would remain).Ref:
GH Actions: harden the workflow against PHPCS ruleset errors
If there is a ruleset error, the
cs2praction doesn't receive anxmlreport and exits with a0error code, even though the PHPCS run failed (though not on CS errors, but on a ruleset error).This changes the GH Actions workflow to allow for that situation and still fail the build in that case.