Project Configuration

CI / CD

Trigger deployments from your own pipeline, protect branches, and skip builds for changes that don't affect your app.

In the dashboardProject → Settings → CI / CD

Deploy tokens

Create a deploy token to trigger deployments from an external CI system (GitHub Actions, GitLab CI, CircleCI). Treat it like a password — store it as a secret in your pipeline.

yaml

# GitHub Actions
- name: Deploy to Deploxa
  run: curl -X POST https://deploxa.com/api/v1/deploy \
    -H "Authorization: Bearer ${{ secrets.DEPLOXA_DEPLOY_TOKEN }}"

For a no-token webhook URL instead, use a deploy hook — the two cover the same need; pick whichever fits your pipeline.

Protected branches

Mark branches as protected so they can't be deployed by accident — useful for keeping a release branch deployable only through a reviewed process.

Deploy ignore patterns

Skip a build when a push only touches files that don't affect your app — docs, tests, CI config. Patterns use micromatch globs. A build is skipped only when every changed file matches an ignore pattern.

text

**/*.md
docs/**
.github/**

For monorepos, combine this with the root directory setting so only changes under your app trigger a build.

GitHub Actions & status checks

Deploxa surfaces your GitHub Actions runs and posts deployment status checks back to commits and pull requests, so the deployment result shows up right in your GitHub workflow.

Deployment Environments CI / CD