Using a tag is a best practice because tags are immutable and represent a fixed version of your

action. By referencing tags, consumers of your action can be assured they are using a stable and

specific version of the action, which helps in avoiding issues with breaking changes.

The commit SHA is another reliable way to specify a particular version of an action. By referencing a

specific commit SHA, consumers can ensure they are using exactly the code that was written at that

moment, avoiding the potential for changes in the future.

The correct syntax includes specifying the job (example-job), the runner (ubuntu-latest), and the

necessary step (npm install -g bats) within the workflow. This ensures that the package is installed

properly during the execution of the job.

The first image shows a workflow trigger with an option for the test suite, and the chosen YAML

configuration matches this interface. Specifically, the test suite input is defined with type: choice and

includes the option value: functional, which aligns with the visible UI elements in the first image.

Once the runner is properly configured and labeled, users should be informed to select the specific

runner by identifying the label or group name when defining the runner in their workflows.

Adding a custom label (like custom-software) to the runner makes it easier for users to select the

runner in their workflows by using the runs-on key, which allows them to choose this specific runner

based on its label.

Creating workflow templates in the organization’s .github repository allows the organization to

standardize workflows and make them easily reusable across multiple repositories. This ensures

consistency and simplifies maintenance.

Creating reusable actions and workflows that can be called from other workflows helps modularize

and standardize automation tasks. These reusable components can be maintained centrally and

called from different workflows across repositories.

To prevent reaching the storage limit for GitHub artifacts and packages, you should manage and

clean up artifacts and packages stored in repositories owned by your organization. This includes

deleting unnecessary artifacts and managing the lifecycle of packages, as they contribute directly to

your organization's storage quota.

The correct syntax for specifying a cleanup script to be run after the main entry point is executed in a Docker-based GitHub Action is to use the post key. This ensures that cleanup.sh runs after the main script (main.sh) has completed.

The matrix configuration specifies two variables: color and animal. The color variable has 2 values

(green and pink), and the animal variable has 2 values (owl and magpie). This would result in 4

combinations (2 color values × 2 animal values). Additionally, the include section introduces two

more combinations (color: blue and animal: owl; color: pink and animal: magpie).

GitHub-hosted runners automatically handle patching, meaning they will be kept up to date with the

latest security updates and software patches for both the runner environment and the underlying

operating system.

GitHub-hosted runners support Linux, Windows, and macOS, giving you flexibility to run workflows

on different operating systems without needing to manage your own self-hosted runners.

You can enable specific actions for the organization by identifying them and providing version

control, ensuring only trusted versions are used in workflows.

GitHub-verified actions can be enabled at the enterprise level, providing an extra layer of security by

ensuring that only trusted actions are available to workflows.

Actions can be published to an internal marketplace, allowing organizations to share reusable actions

securely within their enterprise without exposing them to the public.