Skip to content

Conversation

@continue
Copy link
Contributor

@continue continue bot commented Dec 1, 2025

Summary

This PR adds comprehensive documentation for three new Mission Control integrations:

PostHog Integration

  • Product analytics and feature flag automation
  • Analytics-driven development workflows
  • A/B test analysis and performance monitoring
  • User behavior insights and UX enhancement automation

Atlassian Integration

  • Jira issue management and sprint planning automation
  • Confluence documentation sync
  • Project tracking and release management
  • Code-to-ticket linking and traceability

Netlify Integration

  • Automated deployment management and CI/CD
  • Environment configuration and variable sync
  • Performance monitoring and smart rollbacks
  • Deploy preview testing and site health checks

Changes Made

  • ✅ Created docs/mission-control/integrations/posthog.mdx
  • ✅ Created docs/mission-control/integrations/atlassian.mdx
  • ✅ Created docs/mission-control/integrations/netlify.mdx
  • ✅ Updated docs/mission-control/integrations/index.mdx to list all three new integrations
  • ✅ Updated docs/docs.json navigation to include the new integration pages

Documentation Style

All three integrations follow the established style from GitHub, Sentry, Snyk, and Slack integrations:

  • Overview section with key capabilities card
  • Detailed setup instructions with step-by-step guides
  • Use case examples with specific agent task descriptions
  • Manual and automated workflow guidance
  • GitHub integration examples for combined workflows
  • Comprehensive troubleshooting accordions
  • Links to relevant cookbook guides in the resources section

Testing

  • Documentation renders correctly in Mintlify
  • All internal links work properly
  • Navigation in docs.json is correct
  • Integrations overview page displays all cards

Related Cookbooks

Each integration references its corresponding cookbook guide:

  • PostHog: /guides/posthog-github-continuous-ai
  • Atlassian: /guides/atlassian-mcp-continue-cookbook
  • Netlify: /guides/netlify-mcp-continuous-deployment

This agent session (https://hub.continue.dev/agents/bd87af73-6499-4e20-bdd4-8272b19060f8) was co-authored by bekah-hawrot-weigel and Continue (https://continue.dev).


Summary by cubic

Added Mission Control docs for PostHog, Atlassian (Jira + Confluence), Netlify, plus new pages for Sanity and Supabase. Updated the integrations overview and navigation, added cookbook cross-links, and fixed Mission Control links to the new hub path.

  • New Features

    • New integration docs for PostHog, Atlassian, Netlify, Sanity, and Supabase (setup, use cases, workflows, troubleshooting, resources).
    • Updated integrations/index.mdx to show the new cards and icon tweaks.
    • Added PostHog, Atlassian, and Netlify to docs/docs.json navigation.
    • Added Info callouts in related cookbooks linking to the new integration pages.
  • Refactors

Written for commit c634961. Summary will update automatically on new commits.

- Created comprehensive documentation for PostHog integration covering analytics, feature flags, and data-driven development workflows
- Created Atlassian integration docs for Jira and Confluence automation including issue management, sprint planning, and documentation sync
- Created Netlify integration docs for deployment automation, environment management, and site monitoring
- Updated integrations overview page to include all three new integrations
- Added new integration pages to docs.json navigation

All three integrations follow the established documentation style and include:
- Overview with key capabilities
- Detailed setup instructions
- Multiple use case examples with specific agent tasks
- Manual and automated workflow guidance
- GitHub integration examples
- Comprehensive troubleshooting section
- Links to relevant cookbook guides

Co-authored-by: bekah-hawrot-weigel <[email protected]>
@continue continue bot requested a review from a team as a code owner December 1, 2025 23:59
@continue continue bot requested review from sestinj and removed request for a team December 1, 2025 23:59
@dosubot dosubot bot added the size:XL This PR changes 500-999 lines, ignoring generated files. label Dec 1, 2025
@github-actions
Copy link

github-actions bot commented Dec 1, 2025

⚠️ PR Title Format

Your PR title doesn't follow the conventional commit format, but this won't block your PR from being merged. We recommend using this format for better project organization.

Expected Format:

<type>[optional scope]: <description>

Examples:

  • feat: add changelog generation support
  • fix: resolve login redirect issue
  • docs: update README with new instructions
  • chore: update dependencies

Valid Types:

feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert

This helps with:

  • 📝 Automatic changelog generation
  • 🚀 Automated semantic versioning
  • 📊 Better project history tracking

This is a non-blocking warning - your PR can still be merged without fixing this.

@continue
Copy link
Contributor Author

continue bot commented Dec 1, 2025

@sestinj @bekah-hawrot-weigel - could you please review this PR? Additionally, if Patrick Erichson has a GitHub username, please feel free to add them as a reviewer as requested.

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 5 files

- Added Info callouts to cookbook guides referencing Mission Control integrations
- Follows same pattern as Sentry integration documentation
- Creates clear path for users from CLI workflows to Mission Control automation
- PostHog: Links to product analytics integration
- Atlassian: Links to Jira/Confluence integration
- Netlify: Links to deployment automation integration

Co-authored-by: nate <[email protected]>

Generated with [Continue](https://continue.dev)

Co-Authored-By: Continue <[email protected]>
@continue
Copy link
Contributor Author

continue bot commented Dec 2, 2025

Documentation Updates Added

I've added bidirectional links between the new integration documentation pages and their corresponding cookbook guides to improve discoverability and guide users from CLI workflows to Mission Control automation.

Changes Made

Updated Cookbook Guides:

  • docs/guides/posthog-github-continuous-ai.mdx
  • docs/guides/atlassian-mcp-continue-cookbook.mdx
  • docs/guides/netlify-mcp-continuous-deployment.mdx

What was added:
Each cookbook now includes an Info callout at the beginning (after the "What You'll Build" card) that:

  • References the corresponding Mission Control integration page
  • Explains the relationship between CLI-based workflows and Mission Control automation
  • Encourages users to explore both approaches
  • Follows the same pattern established by the Sentry integration docs

Example

The PostHog cookbook now includes:

The new PostHog Mission Control Integration enables Continuous AI for product analytics - where AI agents autonomously analyze user behavior, identify optimization opportunities, and create data-driven development tasks. This cookbook focuses on CLI-based workflows, but you can also deploy autonomous agents through Mission Control.

This creates a clear path for users to discover Mission Control features while learning about CLI workflows, matching the existing pattern from the Sentry documentation.

@continue
Copy link
Contributor Author

continue bot commented Dec 2, 2025

CI Test Failures Analysis

The failing tests are unrelated to the documentation changes in this PR:

Failed Tests:

  • test (windows-latest, 22) - Failed in TUIChat.editMessage.test.tsx
  • test (macos-latest, 24) - Failed in TUIChat.editMessage.test.tsx

Root Cause:

These are flaky UI tests in the CLI extension (extensions/cli/src/ui/__tests__/TUIChat.editMessage.test.tsx). The specific failure is:

AssertionError: expected '...' not to contain 'No user messages to edit'

This is a timing-related test failure in the Terminal UI component, completely unrelated to:

  • The PostHog integration docs
  • The Atlassian integration docs
  • The Netlify integration docs
  • Updates to index.mdx and docs.json

Evidence:

✅ All other checks passed:

  • Mintlify Deployment - PASS
  • Mintlify Validation - PASS
  • lint - PASS
  • prettier-check - PASS
  • All other test matrices (Ubuntu, macOS 18/20/22, Windows 18/20/24) - PASS
  • VSCode checks - PASS
  • Core checks - PASS
  • E2E tests - PASS

Recommendation:

The failing tests are known to be flaky and would benefit from being fixed separately. This PR's documentation changes are ready for merge. A maintainer with rerun permissions can restart the failed jobs, or merge despite the flaky tests since they're unrelated to this PR.

@RomneyDa RomneyDa requested a review from BekahHW December 3, 2025 23:02
Copy link
Collaborator

@RomneyDa RomneyDa left a comment

Choose a reason for hiding this comment

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

added some nitpicks to start

@github-project-automation github-project-automation bot moved this from Todo to In Progress in Issues and PRs Dec 3, 2025
@RomneyDa RomneyDa marked this pull request as draft December 4, 2025 20:25
@BekahHW BekahHW marked this pull request as ready for review December 8, 2025 19:15
@dosubot dosubot bot added size:XXL This PR changes 1000+ lines, ignoring generated files. and removed size:XL This PR changes 500-999 lines, ignoring generated files. labels Dec 8, 2025
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 20 files

Copy link
Collaborator

@RomneyDa RomneyDa left a comment

Choose a reason for hiding this comment

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

Main things are comment on /hub?type=agents which doesn't take users to mission control, nonexistent "Setup", "Components" concept. I dropped a lot of non blocking opinions too

What if we put continue-overview at overview instead?

It feels like with many of our agent examples in the "what your x integration can do" sections it's not clear that the user would have to create them. We should make that clearer or create them ourselves and link to them.

I think each integration docs page (netlify, sanity, etc) is a bit verbose. If we could cut them by half I think they would be more digestible.


<Step title="🎯 Access Mission Control">
Go to [hub.continue.dev/agents](https://hub.continue.dev/agents) and:
Go to [hub.continue.dev/agents](https://hub.continue.dev/hub?type=agents) and:
Copy link
Collaborator

Choose a reason for hiding this comment

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

/hub?type=agents goes to hub search
Most likely want to go to /integrations/github

Copy link
Collaborator

Choose a reason for hiding this comment

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

This applies to all the changed links here

</Card>

<Card title="Netlify" icon="gauge-high" href="/mission-control/integrations/netlify">
Automate deployments and manage site configuration.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Our recommended agent is "website optimizer" for Netlify, which potentially doesn't match description here

</Card>

<Card title="PostHog" icon="chart-line" href="/mission-control/integrations/posthog">
Leverage product analytics and feature flags for data-driven development.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Maybe a bit more a description of posthog than a description of what our integration does e.g. update dashboards automatically


<Step title="Connect Sanity">

Click Setup -> "Connect" next to Sanity. The integration uses OAuth authentication through the Sanity MCP.
Copy link
Collaborator

Choose a reason for hiding this comment

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

There is no longer a "Setup" button

---

## Overview

Copy link
Collaborator

Choose a reason for hiding this comment

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

This docs page feels a bit verbose, potentially could whittle down quite a bit


<Card title="GitHub Integration" icon="github" href="/mission-control/integrations/github">

Combine Atlassian with GitHub for complete DevOps automation
Copy link
Collaborator

Choose a reason for hiding this comment

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

We kind of "require" Github to integrate Atlassian now

imo "complete devops automation" is a bit of a stretch with Atlassian and Github


Click "Connect" next to PostHog. You'll need the following credentials:

- **Project API Key**: Your PostHog project API key
Copy link
Collaborator

Choose a reason for hiding this comment

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

Posthog calls it "Auth token" rather than API key, similar
Can link to posthog mcp / get auth token pages here

Copy link
Collaborator

@RomneyDa RomneyDa Dec 10, 2025

Choose a reason for hiding this comment

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

EDIT they do call it api key


**How to get these credentials:**
1. Log into your PostHog account
2. Go to **Project Settings****Project API Key**
Copy link
Collaborator

Choose a reason for hiding this comment

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

This might be hallucinated


After analyzing a deploy preview, the agent posts a comprehensive PR comment like this:

```markdown
Copy link
Collaborator

Choose a reason for hiding this comment

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

Posting the full comment example here feels a bit hard to maintain since it's so attached to prompt

Try asking a question:
```
> Tell me about the CLI
Copy link
Collaborator

Choose a reason for hiding this comment

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

Let's cut this overview to a few hundred lines by eliminate the in-the-weeds sections

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

Labels

size:XXL This PR changes 1000+ lines, ignoring generated files.

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

3 participants