diff --git a/docs/docs.json b/docs/docs.json index 1e783f7ee2..5d3a59c22f 100644 --- a/docs/docs.json +++ b/docs/docs.json @@ -261,6 +261,7 @@ "pages": [ "guides/posthog-github-continuous-ai", "guides/continue-docs-mcp-cookbook", + "guides/github-mcp-continue-cookbook", "guides/sanity-mcp-continue-cookbook", "guides/snyk-mcp-continue-cookbook", "guides/dlt-mcp-continue-cookbook", diff --git a/docs/guides/github-mcp-continue-cookbook.mdx b/docs/guides/github-mcp-continue-cookbook.mdx new file mode 100644 index 0000000000..65ea7a3efc --- /dev/null +++ b/docs/guides/github-mcp-continue-cookbook.mdx @@ -0,0 +1,376 @@ +--- +title: "GitHub Issues and PRs with GitHub MCP and Continue" +description: "Use Continue and the GitHub MCP to list, summarize, and act on open issues and recently merged pull requests with natural language prompts." +sidebarTitle: "GitHub Issues with Continue" +--- + + + A GitHub workflow assistant that uses Continue with the GitHub MCP to: + - List, filter, and summarize open issues + - Review and summarize recently merged PRs + - Post comments with AI-generated summaries or checklists + - Automate routine GitHub maintenance with headless CLI runs + + +## Prerequisites + +Before starting, ensure you have: + +- Continue account with **Hub access** +- Read: [Understanding Agents β€” How to get started with Hub agents](/guides/understanding-agents#how-to-get-started-with-hub-agents) +- Node.js 22+ installed locally +- A GitHub account and a repository to work with +- A GitHub token with the appropriate scopes: + - For read-only: `repo:read` + - To comment on issues/PRs: `public_repo` for public repos or `repo` for private repos + +For all options, first: + + + ```bash + npm i -g @continuedev/cli + ``` + + + + Add your `GITHUB_TOKEN` to your [Continue Hub agent's environment variables](https://hub.continue.dev/settings). + + + + + To use agents in headless mode, you need a [Continue API key](https://hub.continue.dev/settings/api-keys). + For write actions (e.g., posting comments), your token must include the relevant GitHub scopes. + + +## GitHub MCP Workflow Options + + + Use the GitHub MCP from Continue Hub for one-click setup, or add it via CLI. + + +After ensuring you meet the **Prerequisites** above, you have two paths to get started: + + + + + + Visit the [Anthropic GitHub MCP](https://hub.continue.dev/anthropic/github-mcp) on Continue Hub and click **Install** to add it to your agent. + + The listing provides a pre-configured MCP block; add your `GITHUB_TOKEN` in Hub. + + + + From your repo root: + ```bash + cn --config continuedev/github-manager-ai + ``` + Now try: "List my open issues labeled bug and summarize priorities." + + + + + You can also attach an MCP to a one-off session: `cn --mcp anthropic/github-mcp`. + + + + + + + Go to the [Continue Hub](https://hub.continue.dev) and [create a new agent](https://hub.continue.dev/new?type=agent). + + + + Install from Hub (recommended) or add YAML manually. Minimal YAML example: + + ```yaml title="config.yaml" + mcpServers: + - name: GitHub MCP + command: npx + args: + - "-y" + - "@modelcontextprotocol/server-github" + env: + GITHUB_TOKEN: ${env:GITHUB_TOKEN} + connectionTimeout: 30 + ``` + + Notes: + - The exact `command`/`args` may differ based on the MCP you choose on Hub. Hub templates prefill these for you. + - Provide `GITHUB_TOKEN` via environment or Hub secrets. + + + + Launch Continue and ask: + ``` + List the 5 most recently updated open issues in this repository. + ``` + + + + + + + To use GitHub MCP with Continue CLI, you need either: + - **Continue CLI Pro Plan** with the models add-on, OR + - **Your own API keys** added to Continue Hub secrets + + The agent will automatically detect and use your configuration along with the GitHub MCP for issue and PR operations. + + + +--- + +## Issue Workflows + +Use natural language to explore, triage, and act on open issues. The agent calls GitHub MCP tools under the hood. + + + **Where to run these workflows:** + - **IDE Extensions**: Use Continue in VS Code, JetBrains, or other supported IDEs + - **Terminal (TUI mode)**: Run `cn` to enter interactive mode, then type your prompts + - **CLI (headless mode)**: Use `cn -p "your prompt" --auto` for automation + + +### Triage and Summaries + + + Get a prioritized overview of current open issues. + +**TUI Mode Prompt:** +``` +List the 20 most recently updated open issues in this repo. +Cluster by label and severity. Summarize top priorities. +``` + +**Headless Mode Prompt:** +```bash +cn -p "List the 20 most recently updated open issues in this repo. Cluster by label and severity. Summarize top priorities." --auto +``` + + + + Narrow by label or assignee. + +**TUI Mode Prompt:** +``` +Show open issues labeled bug or security, assigned to @me. +Summarize blockers and suggest next steps. +``` + +**Headless Mode Prompt:** +```bash +cn -p "Show open issues labeled bug or security, assigned to @me. Summarize blockers and suggest next steps." --auto +``` + + +### Taking Action + + + Post an AI-generated status update or checklist. + +**TUI Mode Prompt:** +``` +Find the issue with the most engagement (comments, reactions) in the last 30 days. +Come up with a triage plan and draft a comment with: +- current hypothesis +- next 2 steps +- owner and ETA +Then post the comment. +``` + +**Headless Mode Prompt:** +```bash +cn -p "Find the issue with the most engagement in the last 30 days. Come up with a triage plan and draft a comment (hypothesis, next 2 steps, owner, ETA) and post it." --auto +``` + + + Requires a token with permission to comment (`public_repo` or `repo`). The agent will confirm before posting unless `--auto` is used. + + + + + Identify issues that need attention. + +**TUI Mode Prompt:** +``` +Find open issues with no activity in the last 30 days. +Suggest action (close, needs-repro, or prioritize) and draft comments. +``` + +**Headless Mode Prompt:** +```bash +cn -p "Find open issues with no activity in the last 30 days. Suggest action and draft comments for each." --auto +``` + + +--- + +## Merged PR Workflows + +Analyze recently merged PRs for change awareness, release notes, and quality signals. + +### Recently Merged Overview + + + Summarize merged PRs over a time window. + +**TUI Mode Prompt:** +``` +List PRs merged in the last 7 days. +Group by area (label or path). Summarize impact and notable changes. +``` + +**Headless Mode Prompt:** +```bash +cn -p "List PRs merged in the last 7 days. Group by area (label or path). Summarize impact and notable changes." --auto +``` + + +### Release Notes + + + Turn merged PRs into crisp release notes. + +**TUI Mode Prompt:** +``` +Generate release notes for PRs merged since tag v1.2.0. +Use keep-a-changelog sections and include PR numbers/authors. +``` + +**Headless Mode Prompt:** +```bash +cn -p "Generate release notes for PRs merged since tag v1.2.0. Use keep-a-changelog sections and include PR numbers/authors." --auto +``` + + +### Deep Dives + + + Get a human-readable summary of a recently merged PR with active discussion. + +**TUI Mode Prompt:** +``` +Find the last merged PR with a significant amount of comments. +Summarize the conversation, including goal, key changes, +risk areas, and any follow-ups. +``` + +**Headless Mode Prompt:** +```bash +cn -p "Find the last merged PR with a significant amount of comments. Summarize the conversation including goal, key changes, risk areas, and follow-ups." --auto +``` + + +--- + +## Automate with GitHub Actions + +Run headless commands on a schedule or in PRs to keep teams informed. + +### Add GitHub Secrets + +Repository Settings β†’ Secrets and variables β†’ Actions: + +- `CONTINUE_API_KEY`: From [hub.continue.dev/settings/api-keys](https://hub.continue.dev/settings/api-keys) +- `GITHUB_TOKEN`: A token with permissions to read issues/PRs and post comments + +### Example Workflow + +Create `.github/workflows/github-mcp-reports.yml`: + +```yaml +name: GitHub MCP Reports + +on: + schedule: + - cron: "0 13 * * 1" # Mondays 13:00 UTC + workflow_dispatch: + pull_request: + types: [opened, synchronize] + +jobs: + report: + runs-on: ubuntu-latest + env: + CONTINUE_API_KEY: ${{ secrets.CONTINUE_API_KEY }} + GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} + steps: + - uses: actions/checkout@v4 + - uses: actions/setup-node@v4 + with: + node-version: "18" + - name: Install Continue CLI + run: npm i -g @continuedev/cli + + - name: Weekly Issue Triage Summary + if: github.event_name == 'schedule' || github.event_name == 'workflow_dispatch' + run: | + cn --config continuedev/github-manager-ai \ + -p "List open issues updated in the last 14 days. Group by label and priority. Propose top 5 actions and include issue links." \ + --auto > issue_summary.txt + + - name: Post PR Context Comment + if: github.event_name == 'pull_request' + env: + PR_NUMBER: ${{ github.event.pull_request.number }} + run: | + REPORT=$(cn --config continuedev/github-manager-ai \ + -p "Summarize the context for PR #${PR_NUMBER}: related open issues, risk areas, and test suggestions. Keep under 200 words." \ + --auto) + gh pr comment ${PR_NUMBER} --body "$REPORT" +``` + + + Use `continuedev/github-manager-ai` consistently throughout your automation as the recommended agent configuration. + + +--- + +## Troubleshooting + +- **Missing or invalid token:** Ensure `GITHUB_TOKEN` is set and has the required scopes. Try a minimal test: β€œList 3 open issues in this repo”. +- **Permissions errors on comment:** Your token must include `public_repo` (public) or `repo` (private) to write comments. +- **Rate limiting:** Reduce frequency or filter queries; consider using a PAT distinct from the default Actions token when running in CI. +- **MCP connection timeout:** If using custom YAML, increase `connectionTimeout` or verify the `command`/`args` from the Hub listing. + +## What You've Built + +After completing this guide, you have a complete **AI-powered GitHub workflow system** that: + +- βœ… Uses natural language β€” Simple prompts for complex GitHub operations +- βœ… Automates issue triage β€” AI analyzes and summarizes open issues +- βœ… Generates release notes β€” Automatic PR digests and changelogs +- βœ… Runs continuously β€” Automated reports via GitHub Actions + + + Your GitHub workflow now operates at **[Level 2 Continuous + AI](https://blog.continue.dev/what-is-continuous-ai-a-developers-guide/)** - + AI handles routine issue triage and PR summaries with human oversight + through review and approval. + + +## Next Steps + +1. **Explore your issues** - Try the issue triage prompts on your repository +2. **Generate release notes** - Use the merged PR prompts to create changelogs +3. **Set up automation** - Add the GitHub Actions workflow to your repo +4. **Customize prompts** - Tailor the prompts to your team's workflow +5. **Monitor progress** - Track issue resolution metrics over time + +## Additional Resources + + + + Anthropic GitHub MCP on Continue Hub + + + How MCP works with Continue agents + + + Pre-configured agent on Continue Hub + + + Official GitHub MCP server README + + + diff --git a/docs/guides/overview.mdx b/docs/guides/overview.mdx index fb0f486e33..8558d8d0be 100644 --- a/docs/guides/overview.mdx +++ b/docs/guides/overview.mdx @@ -20,6 +20,7 @@ description: "Comprehensive collection of practical guides for Continue includin Step-by-step guides for integrating Model Context Protocol (MCP) servers with Continue: - [Continue Docs MCP Cookbook](/guides/continue-docs-mcp-cookbook) - Use the Continue Docs MCP to write cookbooks, guides, and documentation with AI-powered workflows +- [GitHub MCP Cookbook](/guides/github-mcp-continue-cookbook) - Use GitHub MCP to list, filter, and summarize open issues and merged PRs, and post AI-generated comments - [PostHog Session Analysis Cookbook](/guides/posthog-github-continuous-ai) - Analyze user behavior data to optimize your codebase with automatic issue creation - [Netlify Performance Optimization Cookbook](/guides/netlify-mcp-continuous-deployment) - Optimize web performance with A/B testing and automated monitoring using Netlify MCP - [Sanity CMS Integration Cookbook](/guides/sanity-mcp-continue-cookbook) - Manage headless CMS content with AI-powered workflows using Sanity MCP