Skip to content

Conversation

@continue
Copy link
Contributor

@continue continue bot commented Nov 10, 2025

Summary

Adds Reo.dev tracking to Continue documentation to enable
developer activity tracking and analytics.

Changes

  • COMPLETED: Added actual Reo.dev tracking script with
    Client ID: 7aa28ed11570734
  • ✅ Updated docs/reo-tracking.js with production tracking
    snippet
  • ✅ Updated docs/docs.json to include custom JavaScript for
    tracking
  • ✅ Script configured to load from
    https://static.reo.dev/7aa28ed11570734/reo.js
  • ✅ Removed REO_SETUP.md as implementation is now complete

Status: ✅ READY FOR REVIEW

This PR is now complete with the actual Reo.dev tracking
script implemented.

Implementation Details

The tracking script:

  • Uses Client ID: 7aa28ed11570734
  • Loads asynchronously with defer attribute
  • Initializes via Reo.init() with clientID parameter
  • Automatically starts tracking once loaded

Key Pages to Track

The following high-intent pages are recommended for tracking in
the Reo.dev dashboard:

  • /troubleshooting - Troubleshooting guide
  • /reference - API Reference
  • /ide-extensions/install - Installation guide
  • /ide-extensions/*/quick-start - Quick start guides
  • /customize/model-providers/* - Model provider setup
  • /guides/* - All guides

Testing Checklist

  • Added actual Reo.dev tracking snippet
  • Updated docs/reo-tracking.js with production code
  • Test locally with npm run dev
  • Verify script loads in browser DevTools
  • Check console for errors
  • Configure base URL in Reo.dev dashboard
  • Configure key pages in Reo.dev dashboard
  • Deploy and verify on production

Related

Closes #8671


Generated with Continue

Co-Authored-By: Continue [email protected]

This agent session was co-authored by Brian Douglas and Continue.

- Add reo-tracking.js placeholder file for Reo.dev snippet
- Update docs.json to include custom JS for tracking
- Add REO_SETUP.md with detailed setup instructions
- Configure key pages for high-intent tracking

The infrastructure is ready but requires the actual Reo.dev
tracking snippet from the dashboard to be added to
docs/reo-tracking.js to enable tracking.

Fixes #8671

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

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

continue bot commented Nov 10, 2025

CI Status Update

The failing test test (macos-latest, 20) is a flaky test unrelated to this PR:

Failed Test: TUIChat - Message Edit Feature > should maintain UI stability during edit operations [LOCAL MODE]

Why it's unrelated:

  • This PR only modifies documentation files (docs/docs.json, docs/reo-tracking.js, docs/REO_SETUP.md)
  • No code changes were made to the CLI or TUIChat components
  • All other test matrices passed (11/12 combinations):
    • ✅ All Ubuntu tests (Node 18, 20, 22, 24)
    • ✅ All Windows tests (Node 18, 20, 22, 24)
    • ✅ macOS tests on Node 18, 22, 24
    • ❌ macOS Node 20 only (flaky test)

This appears to be a pre-existing flaky test. A maintainer with appropriate permissions can re-run the failed job if needed.

- Replace placeholder with actual Reo.dev tracking script
- Update tracking script with Client ID: 7aa28ed11570734
- Remove REO_SETUP.md as tracking is now implemented
- Script will load from https://static.reo.dev/7aa28ed11570734/reo.js

Closes #8671

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

Co-Authored-By: Continue <[email protected]>
@bdougie bdougie marked this pull request as ready for review November 11, 2025 05:44
@bdougie bdougie requested a review from a team as a code owner November 11, 2025 05:44
@bdougie bdougie requested review from RomneyDa and removed request for a team November 11, 2025 05:44
@dosubot dosubot bot added the size:S This PR changes 10-29 lines, ignoring generated files. label Nov 11, 2025
@github-actions
Copy link

⚠️ 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.

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

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

Labels

size:S This PR changes 10-29 lines, ignoring generated files.

Projects

Status: Todo

Development

Successfully merging this pull request may close these issues.

Add Reo.dev tracking snippet for documentation

2 participants