> Portal Navigation:
> 
> - Append `.md` to any URL under `https://dev.wix.com/docs/` to get its markdown version.
> - Pages are either content pages (article or reference text) or menu pages (a list of links to child pages).
> - To get a menu page, truncate any URL to a parent path and append `.md` (e.g. `https://dev.wix.com/docs/sdk.md`, `https://dev.wix.com/docs/sdk/core-modules.md`).
> - Top-level index of all portals: https://dev.wix.com/docs/llms.txt
> - Full concatenated docs: https://dev.wix.com/docs/llms-full.txt

## Resource: CD Workflows

## Article: CD Workflows

## Article Link: https://dev.wix.com/docs/go-headless/wix-managed-headless/project-development/cd-workflows.md

## Article Content:

# Integrate the Wix CLI into CI/CD Workflows

The Wix CLI can run in any continuous integration and continuous delivery (CI/CD) pipeline, so you can automate tasks like testing and building your headless project on every push or pull request. Because the CLI is a standard command-line tool, it's pipeline-agnostic — the example below uses [GitHub Actions](https://github.com/features/actions) because it's widely used, but the same approach applies to GitLab CI, CircleCI, Jenkins, and other providers.

A common setup is to run your [unit tests](https://dev.wix.com/docs/go-headless/wix-managed-headless/develop-your-project/write-unit-tests.md) automatically on every pull request, so regressions are caught before they're merged.

## Example: run unit tests on every pull request

This GitHub Actions workflow installs your dependencies and runs your unit test script whenever a pull request is opened or updated. Add it to your repository at `.github/workflows/ci.yml`:

```yaml
name: CI PR
on:
  pull_request:
    branches:
      - '*'

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 22.x
          cache: 'npm'

      - name: Install
        run: npm install

      - name: Unit tests
        run: npm run test:unit
```

Replace `test:unit` with the name of the test script defined in your `package.json`.

## Run other CLI commands

The same approach works for any CLI command. For example, you can add a step that runs [`wix build`](https://dev.wix.com/docs/wix-cli/command-reference/project-commands/build.md) to confirm your project compiles as part of your checks.

## See also

- [Write Unit Tests for a Wix CLI Project](https://dev.wix.com/docs/go-headless/wix-managed-headless/develop-your-project/write-unit-tests.md)
- [Build and Deploy a Headless Project with the Wix CLI](https://dev.wix.com/docs/go-headless/wix-managed-headless/develop-your-project/build-and-deploy.md)
- [Wix CLI Command Reference](https://dev.wix.com/docs/wix-cli/command-reference/introduction.md)