GitHub Actions

What it does

The Flagify GitHub Action evaluates a feature flag during your CI run and exposes the result to subsequent steps. Use it to gate deploys, skip test suites, or branch a workflow based on flag state.

Use cases

• Block a production deploy while a flag is still disabled in production.
• Run a longer test suite only when a canary-tests flag is on.
• Warm caches conditionally when a rollout flag is active.
• Tag releases differently when an experiment variant ships.

Quick start

- name: Check feature flag
  id: flag
  uses: flagifyhq/flagify-action@v1
  with:
    api-key: ${{ secrets.FLAGIFY_API_KEY }}
    flag: new-checkout-flow

- name: Deploy
  if: steps.flag.outputs.enabled == 'true'
  run: ./deploy.sh

Kill-switch pattern

Use on-disabled: fail when a flag acts as a gate — the step fails when the flag is off so any dependent job is skipped automatically.

- name: Require production deploys enabled
  uses: flagifyhq/flagify-action@v1
  with:
    api-key: ${{ secrets.FLAGIFY_API_KEY }}
    flag: production-deploys-enabled
    on-disabled: fail

- name: Deploy
  run: ./deploy.sh

Modes for on-disabled:

• continue (default) — emit outputs, proceed. Use if: on later steps.
• fail — fail the step when the flag is off. Good for kill-switches.
• skip — log a notice when off; downstream should gate on outputs.enabled.

Why partner on this

If you run GitHub Actions workflows for your customers, bundling Flagify lets them control rollouts without touching CI config. Co-market the workflow with us — we’ll write the example repo.