The document presents an introduction to GitHub Actions, outlining its core concepts, functionalities, and etiquette for participants in related sessions. GitHub Actions automates workflows and supports CI/CD directly within GitHub, enabling developers to build, test, and deploy code efficiently. It also provides various use cases, emphasizing automation and integration with third-party tools, and highlights the advantages of using a GitHub-native CI/CD tool.

1. Presented By: Rishi Kumar Ray
Introduction to
Github Actions

2. Lack of etiquette and manners is a huge turn off.
KnolX Etiquettes
Punctuality
Respect Knolx session timings, you
are requested not to join sessions
after a 5 minutes threshold post
the session start time.
Feedback
Make sure to submit a constructive
feedback for all sessions as it is
very helpful for the presenter.
Silent Mode
Keep your mobile devices in silent
mode, feel free to move out of
session in case you need to attend
an urgent call.
Avoid Disturbance
Avoid unwanted chit chat during
the session.

3. Agenda
01 What is GitHub Actions?
02 Workflows
03 Why Having Github Native CI/CD tool is helpful
04 Some Use Cases of Github Action
05 Demo

4. What is GitHub Actions?
GitHub Actions gives developers the ability to automate their workflows
across issues, pull requests, and more—plus native CI/CD
functionality.
It was launched in 2018 as to help developers automate their
workflows—all within GitHub.

5. GitHub Actions allows users on GitHub to perform a large
number of actions, such as deploy to AWS, Terraform, Email
the developers if a commit breaks any tests, and much, much
more!
At the most basic level, GitHub Actions brings automation
directly into the software development lifecycle on GitHub via
event-driven triggers.
These triggers are specified events that can range from
creating a pull request to Pushing

6. All GitHub Actions automations are handled via workflows,
which are YAML files placed under the .github/workflows
directory in a repository that define automated processes.
Workflows

7. Every workflow consists of several different core concepts. These include:
Events: Events are defined triggers that kick off a workflow. They can be configured to look for
one or more triggers and qualified as 4 needed by a developer. They can also be set to run on
specific branches within a given repository on GitHub.
Jobs: Jobs are a set of steps that execute on the same runner. Each runs in its own VM and
parallel to other jobs, unless otherwise specified.
Steps: Steps are individual tasks that run commands in a job. These can be an action or a shell
command. All steps in a job execute on the same runner.
Actions: An action is a command that’s executed on a runner—and the core element of GitHub
Actions, which is named after it.
Runners: A runner is a GitHub Actions server. It listens for available jobs, runs each in parallel,
and reports back progress, logs and results. Each runner can be hosted by GitHub or
self-hosted on a localized server. GitHub Hosted runners are based on Ubuntu Linux, Windows,
and macOS.

8. Workflows support a number of different automations ranging from pull requests and branch
merging—plus, third-party integrations with your 5 preferred tools such as chat app
notifications, testing suites, container management, and more via the GitHub Marketplace.
You can leverage automated workflows to build, test, and deploy code directly into a virtual
machine or a Docker container. GitHub Actions also supports “matrix builds,” which enables
you to simultaneously test builds across multiple operating systems and runtime versions.
jobs:
example_matrix:
strategy:
matrix:
version: [10, 12, 14]
os: [ubuntu-latest, windows-latest]

9. Workflows
Events
Pull/Push/Fork/issues
Jobs
Steps
Note: one event can trigger
many workflows, a workflow
can contain many jobs, and a
job can contain many steps.

10. Why having a GitHub-native CI/CD tool is helpful:
The most basic answer is simplicity—if you’re already hosting a project on GitHub, you have a
built-in CI/CD tool that works right alongside your code.
Github Actions is fully integrated into Github and therefore doesn't require and external site. This
means that it can be managed in the same place where your source Code is Present.
It allows you to test your code in different operating systems as well as on container.
Github provides multiple templates for all kinds of CI as well as it also allows you to create your
own templates.
Actions are completely free for every open-source repository and include 2000 free build minutes
per month for all your private repositories which is comparable with most CI/CD free plans.

11. Use Cases of Github Actions
Some of the of the most common use cases for GitHub Actions include:
1. Build, test, and deploy within the GitHub flow
2. Automate repetitive tasks: GitHub Actions can be used to automate an almost endless number of steps in the
software development lifecycle. Whether it’s the creation of a pull request, a new contributor joining your repository
3. Easily add preferred tools and services to your project: GitHub Actions gives you the ability to connect and
integrate your preferred third-party tools and services directly into your repository.
4. Keep track of your projects: You can use GitHub Actions to monitor application builds, measure performance,
track errors and more via integrations with third-party tools.
5: Quickly review & test code on GitHub: GitHub Actions lets you integrate any number of third-party testing tools
directly into your workflow in your repo—at any step. Moreover, GitHub Actions enables multi-container testing and
“matrix builds,” which lets you run multiple tests on Linux, Windows, and macOS at the same time.

12. Demo

13. Thank You !
Get in touch with us:
Lorem Studio, Lord Building
D4456, LA, USA