Discord links across docs, READMEs, GUI components, and issue templates now point to https://github.com/continuedev/continue/discussions. The Discord context provider (product feature) is left untouched. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Continue PR Review Actions
GitHub Actions that provide automated code reviews for pull requests using Continue CLI.
Available Actions
This repository provides a GitHub Action for automated PR reviews:
General Review Action
Provides high-level PR assessment with overall feedback and recommendations.
- Path:
continuedev/continue/actions/general-review@main - Trigger:
@continue-review - Output: Summary comment with strengths, issues, and recommendations
Quick Start
Setting up General Review
name: PR General Review
on:
pull_request:
types: [opened, ready_for_review]
issue_comment:
types: [created]
permissions:
contents: read
pull-requests: write
issues: write
jobs:
review:
runs-on: ubuntu-latest
timeout-minutes: 10
steps:
- uses: continuedev/continue/actions/general-review@main
with:
continue-api-key: ${{ secrets.CONTINUE_API_KEY }}
continue-org: "your-org-name"
continue-config: "your-org-name/review-bot"
Inputs
The action accepts the following inputs:
| Input | Description | Required |
|---|---|---|
continue-api-key |
API key for Continue service | Yes |
continue-org |
Organization for Continue config | Yes |
continue-config |
Config path (e.g., "myorg/review-bot") | Yes |
Setup Requirements
1. Continue API Key
Add your Continue API key as a secret named CONTINUE_API_KEY in your repository:
- Go to your repository's Settings
- Navigate to Secrets and variables → Actions
- Click "New repository secret"
- Name:
CONTINUE_API_KEY - Value: Your Continue API key
2. Continue Configuration
Set up your review bot configuration in Continue:
- Create a configuration for your organization
- Configure the review bot settings
- Note your organization name and config path
3. Workflow Permissions
The workflow requires these permissions:
contents: read- To checkout and read repository codepull-requests: write- To post review comments on PRsissues: write- To respond to comment triggers
Triggering Reviews
The action can be triggered in two ways:
Automatic Triggers
- When a PR is opened by a team member (OWNER, MEMBER, or COLLABORATOR)
- When a PR is marked as "ready for review" by a team member
Manual Triggers
Team members can trigger reviews by commenting on any pull request:
@continue-review- Triggers a review
Review Output
The general review provides a structured comment that includes:
- Strengths: What was done well in the PR
- Issues Found: Categorized by severity (Critical, High, Medium, Low)
- Suggestions: Improvement recommendations
- Overall Assessment: Final recommendation (APPROVE, REQUEST_CHANGES, or COMMENT)
How It Works
- Checks out repository code
- Fetches PR diff using GitHub CLI
- Generates a comprehensive review prompt
- Runs Continue CLI with specified configuration
- Posts review as a PR comment
Versioning
We recommend using the main branch:
@main- Uses the latest code from the main branch
Example:
uses: continuedev/continue/actions/general-review@main
Troubleshooting
Review not triggering
- Ensure the PR author or commenter has appropriate permissions (OWNER, MEMBER, or COLLABORATOR)
- Check that the workflow file is in the default branch
- Verify the Continue API key is correctly set as a repository secret
No review output generated
- Check the action logs for any errors
- Verify your Continue configuration is correct
- Ensure your Continue API key is valid
Support
For issues or questions: