Which set of workflow commands creates annotations at notice, warning, and error severity levels in GitHub Actions logs?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Shell or any step can echo ::notice::, ::warning::, and ::error::—with optional file/line for PR pins. Fake annotate-* names and log groups alone are not the annotation severity trio.
Full explanation below image
Full Explanation
Workflow commands written to stdout drive runner features. ::notice::, ::warning::, and ::error:: create annotations at increasing severity; parameters such as file, line, and col attach them to code locations for the PR Files changed view. Log grouping (::group:: / ##[group]) collapses output but is not a substitute for severity annotations. Debug commands relate to debug logging, not PR error pins. Shell steps are first-class producers of these commands; JS actions often wrap them via @actions/core. Problem matchers auto-generate similar annotations from tool output. Prefer structured annotations over dumping failures only as raw log text.