🌱 Enhance GitHub actions CI #2095
Merged
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.
The GitHub actions CI workflow is run for both pull-requests (targeting the remote branch) and the merge commit push whey they re merged (targeting the branch where they were merged into). Pull-request-related results are exposed under the checks of the PR, which makes them pretty accessible. However, push-related results are only shown in the "Actions" tab and are usually not reviewed. As an example, a linting issue was introduced nearlly a month ago in master, which was passing the PR linting check as it only checks the modified code, but was not passing the push linting check. This means that coverage report was not being sent to coveralls about the master branch since the February 22nd, and we just realized today (March 16th).
This PR adds an additional debugging step that will create an issue if one of the "hidden" GitHub action CI workflows fail with the SHA of the offending commit, the link to the corresponding action execution wher some debugging information will alos be found (secrets are safely removed first).