Skip to content

docs: add GitHub trigger event types for workflows#10213

Open
BekahHW wants to merge 1 commit intomainfrom
docs/remote-config-pr-3083
Open

docs: add GitHub trigger event types for workflows#10213
BekahHW wants to merge 1 commit intomainfrom
docs/remote-config-pr-3083

Conversation

@BekahHW
Copy link
Collaborator

@BekahHW BekahHW commented Feb 5, 2026

That PR adds two new GitHub workflow trigger types:

  • PR Review Comment (pr_review_comment): Triggers when a new review comment is created on a PR
  • Check Failed (check_failed): Triggers when a CI check suite fails

Changes:

  • Added new "GitHub Trigger Event Types" section to /docs/mission-control/integrations/github.mdx
  • Documents all 6 available GitHub trigger event types in a table format
  • Added Info callout explaining the context provided by the new trigger types

Continue Tasks: ▶️ 1 queued — View all


Summary by cubic

Add a "GitHub Trigger Event Types" section to the Mission Control → Integrations → GitHub docs, listing all six supported workflow triggers and documenting the two new events: PR Review Comment and Check Failed. Includes an info callout with the context these new triggers provide (comment file/body/author, failed check names, and links).

Written for commit 87b0a77. Summary will update on new commits.

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 <bekah@continue.dev>
Generated with [Continue](https://continue.dev)

Co-Authored-By: Continue <noreply@continue.dev>
@BekahHW BekahHW requested a review from a team as a code owner February 5, 2026 06:04
@BekahHW BekahHW requested review from RomneyDa and removed request for a team February 5, 2026 06:04
@dosubot dosubot bot added the size:S This PR changes 10-29 lines, ignoring generated files. label Feb 5, 2026
@github-actions
Copy link

github-actions bot commented Feb 5, 2026


Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.


I have read the CLA Document and I hereby sign the CLA


root seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.

Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:S This PR changes 10-29 lines, ignoring generated files.

Projects

Status: Todo

Development

Successfully merging this pull request may close these issues.

1 participant