My Understanding of CI/CD

From what I've learned, Continuous Integration (CI) is a practice that prevents the chaos of developers working in isolation for too long. It encourages us to merge our code into a central place several times a day. As soon as a merge happens, a script runs to build the project and test it. This has been a lifesaver for finding issues before they become big problems.

Continuous Deployment (CD) is the next logical step. It's about automatically releasing the code to the world once it's been proven to work through testing. This creates a smooth, fast flow from writing a line of code to seeing it in action.

My Project's Automation Workflow

I created my own simple pipeline for this site with GitHub Actions. Basically, any time I commit and push a change to my main repository branch, it triggers an automated job. This job handles the deployment process for me, making my site live on GitHub Pages without any manual work.

A Quick Test

Click the button below to see a JavaScript message.