Skip to main content

Skip Trigger.dev deployment via commit message flag

Feature Request

When the GitHub integration is enabled with preview deployments, every push triggers a deploy, there's no way to opt out for a specific PR or commit. Add support for a commit-message marker (similar to Vercel's [skip ci]) so we can skip Trigger.dev deployment on any push we don't want to ship

Posted by Iss Haddad ·
2 comments

Comments2

  • Igor Dimitrijevic

    •

    Jul 10

    One more filter: skip draft PRs.

    Ideal behavior: don't deploy drafts, deploy when a PR is marked ready for review, archive when it's converted back to draft.

  • Iss Haddad

    Team•

    Jul 9

    Broadening this a bit: the underlying need is control over which pushes trigger a deploy when the GitHub integration is enabled, the commit-message flag is one way, but two other common asks fall under the same umbrella:

    1. Skip by branch name: don't deploy pushes to specific branches (or only deploy certain branch patterns).

    2. Skip unless relevant paths changed: in a monorepo, only deploy when files under the Trigger-relevant paths change, ignoring unrelated changes. This mirrors Vercel's "Ignored Build Step."

    Ideally the integration would support all three (commit flag, branch filter, path filter), similar to how Vercel lets you configure ignored build steps. Consolidating them here so they're tracked together.