The Current CI/CD tooling for our company is moving away from Jenkins and towards GitHub Actions. Learn some basics about GitHub Actions as a reulst.
What’s Git Actions
According to Github:
GitHub Actions is a continuous integration and continuous delivery (CI/CD) platform that allows you to automate your build, test, and deployment pipeline. You can create workflows that run tests whenever you push a change to your repository, or that deploy merged pull requests to production.
If you have experience with CI/CD tooling, potentially with Genkins, you can view Github Actions as a similar but better tool to achive the same purpose.
Similarly, GitHub Actions can be used for:
- build and test
 - deployment
 - publish packges
 - manage github(issues, lablels)
 - and so so
 
A Quick Example
1. Create a Github Action Workflow YAML File
In your repository on GitHub, create a workflow file called github-actions-hello-world.yml in the .github/workflows directory.
2. Copy and Paste the Following Hello World YAML Content
 |  | 
Commit the YAML File to the Repo
Committing the workflow file to your branch
View the Workflow Reulst
- On GitHub, navigate to the main page of the repository.
 - Under your repository name, click Actions.
 - In the left sidebar, click the workflow you want to display
 



Compare GitHub Actions with Jenkins
GitHub Actions Impressions
- easy to learn and get started
 - highly integrated with Github and developer friendly
 - SaaS solution and team can choose to not maintain servers for CI/CD.
 - Market place for sharing and reusing workflows
 
Jenkins
- open source software and plug-ins to extend functionality
 - team need to maintain the servers for jenkins and jenkins agents
 - not locked to one source code management platform(Github) and can have code on any repository, including Github, Gitlab, BitBucket, and others.
 - learning curve is more steep