You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice if Spread integrated better with Github Actions. In snapd, we have a problem matcher to convert errors in Spread's output to annotations:
While this is a good start, it has a few deficiencies:
The annotation only reports the single line of the error message.
The annotation has no file name or line number information.
We can't solve either of these via problem matchers, so the alternative would be for Spread to detect it is running under Github Actions (e.g. by checking for the GITHUB_ACTIONS environment variable), and then output error annotations directly with the ::error:: command:
I realise that mapping errors to line numbers in the yaml file would be difficult, but it would be nice to at least associate the error message with the task.yaml file.
Looking at actions/toolkit#193, it seems like it is possible to encode new lines in the annotation message using %0A.
The text was updated successfully, but these errors were encountered:
It would be nice if Spread integrated better with Github Actions. In snapd, we have a problem matcher to convert errors in Spread's output to annotations:
https://github.com/snapcore/snapd/blob/master/.github/spread-problem-matcher.json
While this is a good start, it has a few deficiencies:
We can't solve either of these via problem matchers, so the alternative would be for Spread to detect it is running under Github Actions (e.g. by checking for the
GITHUB_ACTIONS
environment variable), and then output error annotations directly with the::error::
command:https://help.github.com/en/actions/reference/workflow-commands-for-github-actions#setting-an-error-message
I realise that mapping errors to line numbers in the yaml file would be difficult, but it would be nice to at least associate the error message with the
task.yaml
file.Looking at actions/toolkit#193, it seems like it is possible to encode new lines in the annotation message using
%0A
.The text was updated successfully, but these errors were encountered: