Use GITHUB_TOKEN for authentication in workflows
At the start of each workflow job, GitHub automatically creates a unique GITHUB_TOKEN secret to use in your workflow. You can use the GITHUB_TOKEN to authenticate in the workflow job.
Reference:
https://docs.github.com/en/actions/tutorials/authenticate-with-github_token

In GitHub Actions, you can configure four primary types of environment protection rules to control how and when deployments proceed to a specific environment.
These rules include:
[D] Required Reviewers: Specify up to six people or teams who must approve a deployment before it can proceed. Only one reviewer from the list needs to approve to unlock the deployment.
[B] Wait Timer: Set a mandatory delay (from 0 to 43,200 minutes) that must pass after a job is triggered before it can run.
Deployment Branches and Tags: Restrict deployments to only occur from specific branches or those matching certain tag patterns (e.g., main, release/*, or v*).
Custom Deployment Protection Rules: Enable third-party systems or automated tools (via GitHub Apps) to gate deployments based on external data, such as security scan results or ticket status.
Reference:
https://oneuptime.com/blog/post/2026-01-25-github-actions-environment-protection-rules/view

Downloading workflow artifacts
You can download archived artifacts before they automatically expire.
Who can use this feature?
People who are signed into GitHub and have read access to a repository can download workflow artifacts.
Reference:
https://docs.github.com/en/actions/how-tos/manage-workflow-runs/download-workflow-artifacts

Adding an action to your workflow
You can add an action to your workflow by referencing the action in your workflow file. The actions you use in your workflow can be defined in:
[F] The same repository as your workflow file
[C] Any public repository
[B] A published Docker container image on Docker Hub
Note: Adding an action from the same repository [F]
If an action is defined in the same repository where your workflow file uses the action, you can reference the action with either the {owner}/{repo}@{ref} or ./path/to/dir syntax in your workflow file.
Reference:
https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/find-and- customize-actions

Example:
on:
schedule:
- cron: '30 5 * * 1,3'
- cron: '30 5,17 * * 2,4'
Reference:
https://docs.github.com/actions/reference/workflow-syntax-for-github-actions