Skip to content

Re-index Algolia search after GitHub Pages deployment - #637

Merged
nonprofittechy merged 1 commit into
mainfrom
ci/reindex-algolia-after-deploy
Oct 2, 2026
Merged

nonprofittechy merged 1 commit into
mainfrom
ci/reindex-algolia-after-deploy

Conversation

@nonprofittechy

Copy link
Copy Markdown
Member

Search indexing currently runs independently of documentation deployments, leaving newly published changes out of search until the next crawl. This triggers the existing DocSearch crawler after the pages build and deployment workflow successfully publishes gh-pages, including deployments from PRs merged into main.

The workflow also supports manual runs from main, reports missing credentials clearly, and leaves indexing to complete asynchronously in Algolia. README instructions cover the required repository secrets: ALGOLIA_CRAWLER_ID, ALGOLIA_CRAWLER_USER_ID, and ALGOLIA_CRAWLER_API_KEY.

Validation: actionlint passed; mocked shell checks passed for a successful request, each missing secret, and an API failure. A live crawl has not been tested because the crawler secrets still need to be added.

@nonprofittechy
nonprofittechy merged commit 3b49a9e into main Oct 2, 2026
2 checks passed
@nonprofittechy
nonprofittechy deleted the ci/reindex-algolia-after-deploy branch October 2, 2026 22:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant