-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Add PostHog, Atlassian, and Netlify integration documentation #8962
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
- 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]>
|
|
@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. |
There was a problem hiding this 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]>
Documentation Updates AddedI'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 MadeUpdated Cookbook Guides:
What was added:
ExampleThe PostHog cookbook now includes:
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. |
CI Test Failures AnalysisThe failing tests are unrelated to the documentation changes in this PR: Failed Tests:
Root Cause:These are flaky UI tests in the CLI extension ( This is a timing-related test failure in the Terminal UI component, completely unrelated to:
Evidence:✅ All other checks passed:
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
left a comment
There was a problem hiding this 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
There was a problem hiding this 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
There was a problem hiding this 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: |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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 | ||
|
|
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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** |
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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
Summary
This PR adds comprehensive documentation for three new Mission Control integrations:
PostHog Integration
Atlassian Integration
Netlify Integration
Changes Made
Documentation Style
All three integrations follow the established style from GitHub, Sentry, Snyk, and Slack integrations:
Testing
Related Cookbooks
Each integration references its corresponding cookbook guide:
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
Refactors
Written for commit c634961. Summary will update automatically on new commits.