CI/CD

[mudongliang]

CI/CD, which stands for continuous integration and continuous delivery/deployment, aims to streamline and accelerate the software development lifecycle.

Continuous integration (CI) refers to the practice of automatically and frequently integrating code changes into a shared source code repository. Continuous delivery and/or deployment (CD) is a 2 part process that refers to the integration, testing, and delivery of code changes. Continuous delivery stops short of automatic production deployment, while continuous deployment automatically releases the updates into the production environment.

[1] https://www.redhat.com/en/topics/devops/what-is-ci-cd

[mudongliang]

Github CI is really useful to automatically perform some operations or check PR or commits with some rules. Let's add this in our

[inscripoem]

We can start from some samples that are helpful for all projects, such as:

• Build a general application & create release
• Build a website & deploy to custom server (there will be an auto-generated for GitHub Pages, Vercel or Netlify)
• Build Docker image & upload to Docker Hub

The logic of a GitHub Actions Workflow is also fancy, maybe we can explain it from a perspective of Docker (Container Virtualization Technology).

Possible references:

GitHub Actions Official Docs

GitHub Actions 入门教程

使用GitHub Action构建全平台docker镜像

awesome-actions

[mudongliang]

我觉得我们可以整一些推文，说明一下我们的仓库里面是如何使用github action的