From 87b0a7798d5af7aa32afffef28106e892ce96afd Mon Sep 17 00:00:00 2001 From: root Date: Thu, 5 Feb 2026 06:03:51 +0000 Subject: [PATCH] docs: add GitHub trigger event types for workflows Documents the available GitHub trigger event types for Continue workflows: - PR Opened - PR Merged - Label Added - Issue Opened - PR Review Comment (new) - Check Failed (new) Co-authored-by: bekah-hawrot-weigel Generated with [Continue](https://continue.dev) Co-Authored-By: Continue --- docs/mission-control/integrations/github.mdx | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/docs/mission-control/integrations/github.mdx b/docs/mission-control/integrations/github.mdx index cc2d4bfdc9..cf45af46d2 100644 --- a/docs/mission-control/integrations/github.mdx +++ b/docs/mission-control/integrations/github.mdx @@ -44,6 +44,25 @@ The following **official workflow templates** are maintained by the Continue tea Official workflow templates may expand over time as new patterns are validated. You can view, enable, and configure these workflows in **[Mission Control → Integrations → GitHub](https://continue.dev/integrations/github)**. +## GitHub Trigger Event Types + +When creating a workflow with a GitHub trigger, you can choose from the following event types: + +| Event Type | Description | +|------------|-------------| +| **PR Opened** | Triggers when a new pull request is opened | +| **PR Merged** | Triggers when a pull request is merged | +| **Label Added** | Triggers when a specific label is added to an issue or PR | +| **Issue Opened** | Triggers when a new issue is created | +| **PR Review Comment** | Triggers when a review comment is added to a pull request | +| **Check Failed** | Triggers when a CI check suite fails | + + + **PR Review Comment** triggers provide context about the comment including the file path, comment body, and author. **Check Failed** triggers include the names of failed checks and a link to the check details. + + +--- + ## Workflow: GitHub issue → pull request (Cloud Agent) **Problem**: GitHub issues pile up because turning an issue into a tested PR takes time and context switching.