feat(docs): reindex docs on change

[Sg312]

Summary

Reindexes docs on change

Type of Change

• Other: github action

Testing

Manual testing

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 4, 2025 8:24pm
sim	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 4, 2025 8:24pm

[greptile-apps]

Greptile Summary

This PR adds a new GitHub Actions workflow (docs-embeddings.yml) that automatically reindexes documentation embeddings whenever documentation content changes. The workflow is designed to maintain fresh vector embeddings for the documentation search/retrieval system by triggering only when files in the apps/docs/** directory are modified on the main or staging branches.

The workflow integrates with the existing codebase by leveraging an existing TypeScript script (process-docs-embeddings.ts) with a --clear flag to regenerate embeddings from scratch. It follows the established pattern seen in other workflows like build.yml and ci.yml by using environment-specific database URLs - dynamically selecting between DATABASE_URL for main branch and STAGING_DATABASE_URL for staging branch deployments.

The automation fits into the broader CI/CD pipeline by ensuring that documentation changes are immediately reflected in the search functionality without manual intervention. This is particularly important for a documentation system that relies on vector embeddings for content discovery and retrieval.

Confidence score: 2/5

• This PR has significant technical issues that could cause workflow failures and should not be merged without fixes
• Score reflects critical syntax errors in shell scripting and redundant conditional logic that could lead to runtime failures
• Pay close attention to the job condition syntax on line 43 and the redundant branch filtering logic on line 14

_{1 file reviewed, 1 comment}

_{Edit Code Review Bot Settings | Greptile}