Variables reference
Find information for supported variables, naming conventions, limits, and contexts in GitHub Actions workflows.
Variables include:
* GITHUB_REPOSITORY
The owner and repository name. For example, octocat/Hello-World
* Etc.
Reference:
https://docs.github.com/en/actions/reference/workflows-and-actions/variables

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).

The core.warning() function from the @actions/core package is used to create a warning message in the workflow logs. This is an annotation type that informs users about issues that don't require failing the build but still need attention.

Monitoring and troubleshooting self-hosted runners
You can monitor your self-hosted runners to view their activity and diagnose common issues.
[A] Reviewing the self-hosted runner application log files
You can monitor the status of the self-hosted runner application and its activities. Log files are kept in the _diag directory where you installed the runner application, and a new log is generated each time the application is started. The filename begins with Runner_, and is followed by a UTC timestamp of when the application was started.
[D] You can choose one of the standard GitHub-hosted runner options or, if you are on the GitHub Team or GitHub Enterprise Cloud plan, you can provision a runner with more cores, or a runner that's powered by a GPU processor. These machines are referred to as "larger runner." Reference:
https://docs.github.com/en/actions/how-tos/manage-runners/self-hosted-runners/monitor-and- troubleshoot
https://docs.github.com/en/actions/concepts/runners/github-hosted-runners

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.