Automated CI/CD Workflow – FlowChart
- Push your changes which we be event for our workflow.
- All the jobs will be automated which are mentioned in workflow like Checkout, setup app, and upload new code.
- Deploy all the changes which is the last job in the workflow.
- Keep track of all your logs to check if CI is working or not.
How To Create A Basic CI Workflow Using GitHub Actions?
GitHub Actions is a continuous integration and continuous delivery (CI/CD) feature provided by GitHub that allows you to automate your build, test, and deployment pipeline whenever any changes happen in your repo.
Continuous integration (CI) is a software development practice in which you merge/commit your changes to the main branch many times a day. For every change, you have to deploy the whole project again and again to reflect changes in the production environment. This can lead to a decrease in productivity and repetition of tasks.
To eliminate this we have something called CI/CD workflow which allows us to build & deploy our code automatically if any changes happen in a production environment.
In this article, we will create a basic CI workflow where we will make changes to Static HTML and deploy it automatically if we push modified code on GitHub pages. GitHub actions already provide some pre-build workflow for HTML, Node.js, Python, etc.
Contact Us