feat: call revalidate index endpoint after content-indexer #965
Conversation
🌿 Documentation Preview
|
There was a problem hiding this comment.
Pull request overview
This PR adds automatic cache revalidation after content indexing to ensure frontend data stays synchronized. When content indexers complete, they now trigger the revalidation endpoint to update cached indices and navigation trees, preventing stale sidebar navigation issues across different pages.
Changes:
- Added revalidation API calls to all three content indexing workflows
- Implemented error handling and logging for revalidation responses
- Configured dynamic navigation tree detection for main content workflow
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
.github/workflows/index-sdk-references.yml |
Adds revalidation step for SDK index and wallets navigation tree after SDK reference indexing |
.github/workflows/index-main-content.yml |
Adds revalidation step with dynamic nav tree extraction from docs.yml after main content indexing |
.github/workflows/index-changelog.yml |
Adds revalidation step for changelog index after changelog indexing |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b5ada521f8
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
2 participants
Description
After content-indexer runs in main, this will call the new revalidate index endpoint to ensure the newly indexed content is now fetched by the frontend. This ensures that sidebar navs for example update in tandem: so its not possible for different pages in the same tab to have different sidebar navs (because one is out of date).
Related Issues
Changes Made
Testing
pnpm run validate)