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
Currently, when "output-to" input is set to "step-summary", there is no way to see stack traces of detected errors, as such information is contained only in "Annotation Raw output" button.
While this button is available only in "Check" page.
I would like to suggest either have additional input to select if need error message or error details displayed in "Summary" page.
The logic responsible for this is located here const lines = (tc.error.message ?? getFirstNonEmptyLine(tc.error.details)?.trim())
The goal is to have tc.error.details by default.
The text was updated successfully, but these errors were encountered:
Thank you @dboriichuk , i'd be more than happy to review and approve a PR with the recommended changes. Would you be interested in submitting a PR that includes the functionality that you're looking for?
Currently, when "output-to" input is set to "step-summary", there is no way to see stack traces of detected errors, as such information is contained only in "Annotation Raw output" button.
While this button is available only in "Check" page.
I would like to suggest either have additional input to select if need error message or error details displayed in "Summary" page.
The logic responsible for this is located here
const lines = (tc.error.message ?? getFirstNonEmptyLine(tc.error.details)?.trim())
The goal is to have
tc.error.details
by default.The text was updated successfully, but these errors were encountered: