Download Latest GH-200 Questions

GitHub workflow commands use the syntax ::command parameter=value::{message}. For an error annotation without file-location metadata, echo " ::error::There was an error " is valid because error is the workflow command and the text following the second :: is the message. GitHub also supports parameters such as file, line, and col, making option C valid for associating the error annotation with a specific source-code position. Option A incorrectly places the actual text in a message= parameter while leaving no message after the command separator. Option D also uses invalid workflow-command syntax because error=... is not the command format GitHub defines. Therefore, according to the current GitHub Actions workflow-command specification, the two valid commands are B and C.

================

A TypeScript-based GitHub Action is implemented as a JavaScript action because TypeScript is compiled or bundled into JavaScript before execution by the GitHub Actions runner. JavaScript actions use an action.yml metadata file whose runs.using value specifies a supported Node.js runtime and whose runs.main property identifies the generated JavaScript entry point, commonly a file under dist. This approach allows the action to run directly on supported Linux, Windows, and macOS runners without requiring a separate Docker container. A composite action is intended primarily to combine reusable workflow steps, while a Bash script action is not a distinct metadata action type. Docker container actions are appropriate when a packaged container environment is specifically required. Therefore, a custom action authored in TypeScript should be packaged and distributed as a JavaScript action.

================

Documentation helps action consumers understand both what an action does and how to invoke it correctly. GitHub specifically recommends creating a README.md when publishing or sharing an action. Recommended content includes a detailed description of the action, required and optional inputs and outputs, secrets and environment variables used by the action, and an example showing how the action is referenced from a workflow. Therefore, documentation directly provides users with the action ' s description and practical usage examples. It does not automatically generate a README in the consuming repository or workflow, and documentation itself does not enable YAML autocomplete. Those capabilities are unrelated to ordinary action documentation. Clear documentation is especially important for reusable actions because consumers must understand expected inputs, outputs, permissions, and version references without inspecting the implementation source code.

================

The workflow_dispatch event is used to manually trigger a workflow run in GitHub Actions. You can specify this event in the workflow file to allow users to manually trigger the workflow from the GitHub UI, often with optional input parameters.