Skip to content

fix: Remove GH Action portion of guide #8036

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Sep 30, 2025
Merged

fix: Remove GH Action portion of guide #8036

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
217 changes: 7 additions & 210 deletions docs/guides/posthog-github-continuous-ai.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -221,218 +221,15 @@ Create missing labels in your repo at: **Settings → Labels → New label**
</Warning>

<Info>
**What Continue CLI Does:** - Parses your analysis results automatically -
Makes authenticated GitHub API calls using your stored token - Creates
properly formatted issues with appropriate labels - Checks for duplicate
issues to avoid spam - Provides confirmation with issue URLs
</Info>

## Setting Up Automated GitHub Actions Workflow

Create a GitHub Actions workflow that runs your Continue CLI analysis automatically on a schedule.

### Add GitHub Secrets

First, add these secrets to your GitHub repository:

1. Go to **Repository Settings → Secrets and variables → Actions**
2. Click **"New repository secret"** and add:
- `CONTINUE_API_KEY`: Your Continue API key from hub.continue.dev
**What Continue CLI Does:**
- Parses your analysis results automatically
- Makes authenticated GitHub API calls using your stored token
- Creates properly formatted issues with appropriate labels
- Checks for duplicate issues to avoid spam
- Provides confirmation with issue URLs

### Create GitHub Actions Workflow

Create `.github/workflows/posthog-analysis.yml` in your repository:

<Tabs>
<Tab title="⚡ Using Pre-Built Agent (Recommended)">
```yaml
name: PostHog Session Analysis with Continue CLI Agent

on:
schedule: - cron: "0 6 \* \* \*" # Run at 6 AM UTC daily
workflow_dispatch: # Allow manual triggering

jobs:
analyze:
runs-on: ubuntu-latest

permissions:
contents: read
issues: write

steps:
- uses: actions/checkout@v4

- name: Set up Node.js
uses: actions/setup-node@v4
with:
node-version: "18"

- name: Install Continue CLI
run: |
npm install -g @continuedev/cli
echo "✅ Continue CLI installed"
cn --version

- name: Authenticate with Continue CLI
run: |
# Set Continue API key
export CONTINUE_API_KEY="${{ secrets.CONTINUE_API_KEY }}"
# Login to Continue CLI
if ! cn auth login --api-key "$CONTINUE_API_KEY"; then
echo "❌ Failed to authenticate with Continue CLI"
exit 1
fi
echo "✅ Continue CLI authenticated"

- name: Load PostHog GitHub Agent
run: |
echo "🤖 Loading PostHog GitHub Continuous AI Agent..."
cn --config continuedev/awesome-models-posthog-gh
echo "✅ Agent loaded successfully"

- name: Run PostHog Analysis and Create GitHub Issues
run: |
echo "🎬 Starting automated PostHog session analysis..."

# Run the agent with the simple prompt
cn -p "Tell me about my PostHog session recordings and create GitHub issues based on the problems."

echo "✅ Analysis and issue creation completed"

- name: Summary
run: |
echo "✅ PostHog analysis workflow completed!"
echo "📊 Check the artifacts for detailed analysis results"
echo "🐛 Check your repository issues for newly created UX issues"
echo "🤖 Agent automatically handled both analysis and issue creation"
```

</Tab>

<Tab title="🛠️ Manual Setup Version">

```yaml
name: PostHog Session Analysis with Continue CLI Manual

on:
schedule: - cron: "0 6 \* \* \*" # Run at 6 AM UTC daily
workflow_dispatch: # Allow manual triggering

jobs:
analyze:
runs-on: ubuntu-latest

permissions:
contents: read
issues: write

steps:
- uses: actions/checkout@v4

- name: Set up Node.js
uses: actions/setup-node@v4
with:
node-version: "18"

- name: Install Continue CLI
run: |
npm install -g @continuedev/cli
echo "✅ Continue CLI installed"
cn --version

- name: Authenticate with Continue CLI
run: |
# Set Continue API key
export CONTINUE_API_KEY="${{ secrets.CONTINUE_API_KEY }}"
# Login to Continue CLI
if ! cn auth login --api-key "$CONTINUE_API_KEY"; then
echo "❌ Failed to authenticate with Continue CLI"
exit 1
fi
echo "✅ Continue CLI authenticated"

- name: Run PostHog Session Analysis
run: |
echo "🎬 Starting PostHog session analysis..."
# Create the analysis prompt
I need you to help me analyze PostHog session recordings to identify UX issues. Please:

1. First, fetch session recordings from PostHog using these details:
- Use the POSTHOG_API_KEY, POSTHOG_PROJECT_ID, and POSTHOG_HOST from my secrets
- API endpoint: {POSTHOG_HOST}/api/projects/{POSTHOG_PROJECT_ID}/session_recordings/?limit=20
- Include Authorization header: 'Bearer {POSTHOG_API_KEY}'

2. Filter the sessions to find problematic ones with either:
- console_error_count > 0 (JavaScript errors)
- recording_duration > 300 (sessions longer than 5 minutes)

3. Analyze the filtered sessions and create exactly 3 GitHub issues for the most critical UX problems.

4. Format each issue like this:
### 1. **Issue Title Here**
**Problem**: One sentence describing the user problem
**Technical Causes**: Brief technical explanation
**Affected Pages**: List the URLs
**Recommended Fix**:
- Specific action item 1
- Specific action item 2
**Priority**: **HIGH** or **MEDIUM** or **LOW**
**Impact**: Quantify the impact (e.g., 'Affects 80% of sessions')

Please make the API call, analyze the data, and provide the 3 formatted issues. Base all recommendations on actual patterns in the session data.
EOF

echo "✅ Analysis completed"


- name: Create GitHub Issues from Analysis
run: |
echo "📝 Creating GitHub issues from analysis..."
# Create the issue creation prompt
I have analyzed PostHog session data and identified UX issues. Now I need you to create GitHub issues using the GitHub API.

For each issue in my analysis:
1. Parse the issue title, body content, and priority level
2. Create a GitHub issue via API POST to: https://api.github.com/repos/{owner}/{repo}/issues
3. Use these headers:
- Authorization: token {GITHUB_PAT}
- Accept: application/vnd.github.v3+json
- Content-Type: application/json
4. Set labels based on priority:
- HIGH: ["bug", "high-priority", "user-experience", "automated"]
- MEDIUM: ["enhancement", "medium-priority", "user-experience", "automated"]
- LOW: ["low-priority", "user-experience", "automated"]
5. Format the issue title as: "🔍 UX Issue: {original title}"

Please create the GitHub issues and confirm they were successfully created with issue numbers and URLs.

echo "✅ Issue creation completed"

- name: Summary
run: |
echo "✅ PostHog analysis workflow completed!"
echo "🐛 Check your repository issues for newly created UX issues"
```

</Tab>
</Tabs>

### Test the GitHub Actions Workflow

1. **Manual Trigger**: Go to **Actions** tab in your repository and manually trigger the workflow
2. **Check Artifacts**: Download the analysis results from the workflow run
3. **Verify Issues**: Check that GitHub issues were created in your repository

<Check>

**Success Indicators:**
- PostHog API returns session data (not empty)
- Continue CLI generates analysis with identified issues
- GitHub issues are created with proper labels and formatting
- Workflow completes without errors
</Info>

</Check>

## What You've Built

Expand Down
Loading