Documentation structure for LLMs (llms.txt)
CircleCI Logo

Cursor Origin trigger event options Beta

3 hours ago
Cloud

When you create a trigger for a Cursor Origin pipeline, you choose the event that runs your pipeline from a set of preset options. Using these options you can trigger a pipeline on pushes, tag pushes, and a range of pull request events.

The Cursor Origin integration is in beta. Cursor Origin is available for circleci type organizations only. For an overview of the integration, see the Users, Organizations, and Integrations Guide.

Introduction

CircleCI projects have pipelines and triggers.

  • Pipelines define the various CI/CD 'units' of work that make up your project.

  • Triggers define when and how to initiate a pipeline.

When you create a Cursor Origin project, CircleCI sets up your first pipeline and one Cursor Origin trigger. That first trigger uses the All pushes event by default, and you can change it during project creation. For the project creation steps, see the Create a Project page.

You set up one trigger during project creation. Once your project exists, you can configure additional triggers under Project settings  Project Setup. See the Set up Triggers page for more information.

Supported trigger options

Select a trigger event from the dropdown under "When would you like to run your pipeline?". The following preset options are available:

  • All pushes: Trigger your pipeline on all pushes to your repository. CircleCI selects this option by default.

  • Tag pushes: Trigger a pipeline on pushes to tags only. When choosing this option, you also need to define tag filters in your config file.

  • Pushes to default branch: Trigger a pipeline on pushes to the default branch only.

  • PR opened: Trigger a pipeline when a pull request is opened.

  • Non-draft PR opened: Trigger a pipeline when a non-draft pull request is opened. Draft pull requests do not trigger a pipeline.

  • PR opened or pushed to, default branch and tag pushes: Trigger a pipeline on four kinds of event. These are pushes to a branch with an open pull request, a pull request being opened, pushes to any tag, and pushes to the default branch. Reopening a closed pull request also triggers a pipeline.

  • PR marked ready for review: Trigger a pipeline when a pull request is taken out of draft mode and marked ready for review.

  • Pushes to open non-draft PRs: Trigger a pipeline when there is a push to a branch with an open pull request that is not in draft mode.

  • PR merged: Trigger a pipeline when a pull request is merged only.

  • PR merged or closed: Trigger a pipeline when a pull request is merged or closed.

These options match the equivalent GitHub Trigger Event Options.

Other ways to trigger a Cursor Origin pipeline

As well as Cursor Origin events, you can start a Cursor Origin pipeline using:

For the full list of events that can trigger a pipeline, see the Trigger a Pipeline page.

Configuration files in Cursor Origin

Your trigger runs a pipeline defined by a config file in your repository. You add that file yourself, and you set its path when you create your project. See the Create a Project page.

For guidance on creating a config file, see the following pages:

See also