How to setup continuous integration and deployment workflows for a web application using GitHub actions
Among others, continuous integration (CI) and continuous deployment (CD) have been since day one standard steps in our quality assurance (Q&A) process for all our projects. Being heavy users of git, specially GitHub we couldn’t wait to get our hands into GitHub actions and experiment if it could be a good fit for our Q&A process. According to GitHub: GitHub Actions makes it easy to automate all your software workflows, now with world-class CI/CD. Build, test, and deploy your code right from GitHub. Make code reviews, branch management, and issue triaging work the way you want. We decided to try it on a ReactJS project and evaluate if it could be part of our tool belt. Expected End Result A very common setup we use in our projects is to have a production and a staging environment, we mirror these environments with two branches: master — contains the source for the production environment , containing the live system being used by the end users develop — contains the sour