Continuous Deployment and Workflow Automation using Github Actions
Github Actions makes it easy for developers to automate software workflows.
Before Github Actions, we had to use a CI/CD tool like Jenkins to trigger a build every time code is pushed to the repository. We also use to integrate these builds with plugins for code quality checks like Sonar.
These activities are usually performed by a designated DevOps team. On the other hand, consider an open-source project, one that runs purely from the support of contributors, how would you make sure the code quality is not degraded with too many people contributing to a project or that functionality is not broken by a new fix?
Github Actions helps us fix that issue. We can take actions based on the events that take place at the repository like push, PR, etc.
Let’s see how to configure a workflow in our project.
The end goal of each workflow depends on the use case but the most commonly used workflow is CI/CD. You can also define more than one workflow, one for deployment, one to send out a greeting message, and so on.
