CI/CD with Github Actions

Question 1

What is the purpose of GitHub Actions?

Answer 1

Automate, customize, and execute software development workflows directly in your GitHub
repository.

Question 2

What are triggers for Github Actions?

Answer 2

Respond to repository events such as push, pull requests, and releases.

Question 3

What are the core components of Github Actions?

Answer 3

Workflows and Events.

Question 4

What are Workflows?

Answer 4

Automated procedures that are configured with YAML files in the .github/workflows directory of a repository.

Question 5

What are events?

Answer 5

Specific activities in a repository that trigger workflows, such as commits, branch or tag creation, issue creations, etc.

Question 6

What are the Core Components of GitHub Actions?

Answer 6

Jobs, Steps and Actions.

Question 7

What are Jobs?

Answer 7

Sets of steps that execute on
the same runner, which can run
sequentially or in parallel.

Question 8

What are Steps?

Answer 8

Individual tasks that run
commands or actions within a job.

Question 9

What are Actions?

Answer 9

Standalone commands that are
combined into steps to create a job.
Actions can be reused and shared
within the GitHub community.