Learning GitHub Actions for DevOps CI/CD - GitHub Environments | How to Add Manual Approvals

The video tutorial explains how to use GitHub environments for deployment, including setting up protection rules like manual approval and wait times. It highlights the differences between repository and environment secrets, emphasizing the benefits of using environment secrets for consistency across different deployment stages. The tutorial also demonstrates how to implement these environments in GitHub workflows, ensuring secure and efficient deployment processes.

What is the purpose of configuring environments with protection rules and secrets in GitHub?

• To increase the speed of workflow execution

• To ensure secure and controlled deployment processes

• To allow public access to the repository

• To enhance the visual appearance of the repository

How can environment protection rules help prevent accidental deployments?

• By automatically deleting the workflow

• By sending email notifications to all users

• By requiring manual approval and adding wait times

• By disabling the run button

What is the maximum wait time that can be set for a job in GitHub environment protection rules?

• 10 days

• 20 days

• 30 days

• 40 days

What is a limitation of using repository-level secrets in GitHub?

• They are not secure

• They require manual updates

• They cannot be used in workflows

• They are limited to a single environment

How do GitHub Environment secrets improve workflow consistency?

• By automatically generating passwords

• By providing a visual interface for secret management

• By allowing the same secret to be used across different environments

• By encrypting all workflow files

In a GitHub workflow, what happens if a secret is not found in the specified environment?

• The workflow sends an error notification

• The workflow skips the step

• The secret is retrieved from the repository-level secrets

• The workflow fails immediately

What must be done before a deployment can proceed if a required reviewer protection rule is in place?

• The environment must be deleted

• The workflow must be restarted

• The repository must be cloned

• The specified reviewer must approve the deployment