[B] Use caching when you want to reuse files that don't change often between jobs or workflow runs, such as build dependencies from a package management system.
[D] Use artifacts when you want to save files produced by a job to view after a workflow run has ended, such as built binaries or build logs.
Reference:
https://docs.github.com/en/[email protected]/actions/tutorials/store-and-share-data

Self-hosted Runners: These run on your own infrastructure (on-premises or cloud). They are primarily used when you need specific environment configurations, such as custom hardware (GPUs), specific operating systems, or access to internal resources behind a firewall.
Using self-hosted runners is a standard solution for accessing private internal network resources, as they can be placed directly within your on-premises or cloud-based private network.
Incorrect:
[Not B]
For GitHub Actions workflows with no specific environment configurations that must be triggered on GitHub-hosted infrastructure, you should typically use GitHub-hosted runners, not self-hosted ones.
Reference:
https://github.blog/enterprise-software/ci-cd/when-to-choose-github-hosted-runners-or-self- hosted-runners-with-github-actions

Local GitHub Actions refer to two concepts: custom actions developed within your own repository and the process of running any GitHub Action locally on your machine for faster testing and debugging.
1. Local Actions (within your repository)
Definition:
These are custom actions that you define and store directly in your repository under the .github/actions/ directory. They are not publicly shared, unlike actions from the GitHub Marketplace.
Purpose:
They are used for project-specific, repetitive tasks that you want to reuse within your workflows without publishing them globally.
How it works:
You can call these local actions in your workflow files as if they were standard published actions.
2. Running Actions Locally (on your development machine)
Note:
Pinned repositories
You can give users easy access to important or frequently used repositories, by choosing up to six repositories for public users and six repositories for members of the organization. Once you pin repositories to your organization profile, the "Pinned" section is shown above the
"Repositories" section of the profile page.
Reference:
https://dev.to/codenamegrant/supercharging-your-workflows-with-local-github-actions-2o23
https://docs.github.com/en/organizations/collaborating-with-groups-in-organizations/customizing- your-organizations-profile

GitHub Actions allows you to configure environment protection rules, where you can require specific users or teams to approve the deployment before the workflow proceeds to the next step.
This ensures that the required reviewers approve the workflow before any sensitive actions (such as deployment) occur.
Note: Managing environments for deployment
You can create environments and secure those environments with deployment protection rules. A job that references an environment must follow any protection rules for the environment before running or accessing the environment's secrets.
Optionally, you can specify people or teams that must approve workflow jobs that use this environment.
Select Required reviewers.
Enter up to 6 people or teams. Only one of the required reviewers needs to approve the job for it to proceed.
Optionally, to prevent users from approving workflows runs that they triggered, select Prevent self-review.
Click Save protection rules.
Reference:
https://docs.github.com/en/actions/how-tos/deploy/configure-and-manage-deployments/manage- environments

[B] If you want your GitHub Enterprise Server instance to use third-party custom actions, you need to enable GitHub Connect.
[C] Most official GitHub-authored actions are automatically bundled with GitHub Enterprise Server, and are captured at a point in time from GitHub Marketplace.
[F] Third-party actions can be manually synchronized to GitHub Enterprise Server (GHES) to be used in workflows without requiring an internet connection to GitHub.com. This is done using the actions-sync tool to download actions from GitHub.com and transfer them to the GHES instance.
This manual method provides an alternative to using GitHub Connect, offering stricter control over which actions are available on the GHES instance.
Reference:
https://docs.github.com/en/[email protected]/get-started/exploring-integrations/about- using-integrations
https://docs.github.com/en/[email protected]/admin/managing-github-actions-for-your- enterprise/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise