To create an effective CI/CD process, it should be possible to triggeraCodefreshpipeline execution not only on code repository events (like`push` or`PR`), but also on any "interesting" CD-related event, coming from some external system.

To create an effective CI/CD process, it should be possible to trigger Codefreshpipelines not only on code repository events (like`push` or`PR`), but also on any "interesting" CD-related event, coming from some external system.

Codefresh not only allows you to define different pipelines on a single project butitalso offers you the capability to trigger them with completely separate mechanisms.

Codefresh not only allows you to define different pipelines on a single project but also offers you the capability to trigger them with completely separate mechanisms. You can even skip triggering a pipeline by including predefined flags in the commit message.

You can easily disable a trigger manually if you don't want to be active anymore.

On the triggers tab click the gear icon on the top right (*Open advanced options*).

{% include image.html

lightbox="true"

file="/images/pipeline/triggers/enable-triggers.png"

Then click the toggle switch on each trigger that you want to enable/disable. You can later enable the same trigger again

by clicking the same switch.

The default behavior triggers the pipeline on a commit action.

Override the default behavior by adding any one of the predefined strings anywhere in the commit message.

*[Creating pipelines]({{site.baseurl}}/docs/configure-ci-cd-pipeline/pipelines/)

**Trigger Name* - a freetext trigger name (required).

**Description* - a freetext description (optional).

**Repository* - you can select any repository even something different than the one that is used for the code checkout.

**Commit Checkbox* - if enabled will trigger this pipeline for any commit.

**Commit Checkbox* - if enabled will trigger this pipeline for any commit, unless the commit message includes any one of the predefined flags in the commit message.

**PR Checkboxes* - various checkboxes for filtering the Pull request event.

The commit checkbox (by default it is enabled) means that this pipeline will run for*any* commit as long as its source branch matches the naming scheme. This includes commits on pull requests.

{% include image.html