ไปป์ไลน์ CI/CD ด้วย GitHub Actions

Continuous Integration (CI) automatically builds and tests your code on every push. Continuous Delivery/Deployment (CD) automatically ships passing code to production.

Together they catch bugs early and remove manual, error-prone release steps.

GitHub Actions runs workflows directly in your repository. There is no separate server to manage, it integrates with pull requests, and it has a generous free tier for public repos.

Workflows are YAML files inside .github/workflows/. Each file describes one workflow, and a repo can have many.

The on key defines what starts a workflow. Common triggers are pushes and pull requests to specific branches.

A workflow has one or more jobs. Each job runs on a fresh virtual machine (a runner) you select with runs-on.

A job is a sequence of steps. A step either runs a shell command (run) or uses a prebuilt action (uses).

The official setup-node action installs the Node version you specify and can cache dependencies for faster runs.

With Node ready, install dependencies and run your test suite. If tests fail the job fails, blocking the merge.

Here is a full, minimal pipeline that checks out code, sets up Node, installs, and tests on every push and pull request.

Never commit API keys. Store them in your repo's Settings > Secrets and reference them with the secrets context. They are masked in logs.

For CD, add a job that runs only after tests pass and only on the main branch, then deploys. The needs and if keys control ordering and conditions.

Test your CI/CD knowledge.

You built an automated pipeline with GitHub Actions:

• Workflows live in .github/workflows/ as YAML
• on sets triggers; jobs run on runs-on runners
• Steps use prebuilt actions or run shell commands
• Install with npm ci and run npm test automatically
• Store credentials in secrets and gate deploys with needs + if

Now every push is tested and safe code can ship automatically.