The smallest scope for an environment variable is within a step. Environment variables defined

within a step are only accessible to that particular step, which makes it the smallest scope for a

variable in a GitHub Actions workflow.

GitHub Actions supports the use of service containers, which allows you to spin up a PostgreSQL

database (or any other service) in a Docker container during your workflow. You can pull a

PostgreSQL image from Docker Hub, and the container will automatically be available to your

workflow job. This method requires no additional infrastructure and is easy to configure and

maintain, as you simply define the container in the workflow file.

A . Use the actions/setup-docker action

B . Authenticate to the GitHub Container Registry.

C . Build the container image.

D . Push the image to the GitHub Container Registry

E . Pull the image from the GitHub Container Registry.

First, the dataset should be encrypted before being stored. This ensures that the data is protected when stored in a repository. The encrypted dataset can be stored in a GitHub secret, ensuring it is securely kept and not exposed publicly. The encryption key needed to decrypt the dataset should also be stored in a GitHub secret to maintain security during the workflow, allowing access only when needed.

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.