Automate crawler #4385
Merged
Automate crawler #4385
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
github-actions
bot
added
the
size: small
|
Check your created Crawler Check your created index on your Algolia Application |
mirnawong1
approved these changes
Nov 3, 2023
There was a problem hiding this comment.
hey @JKarlavige ! this looks good to me - i couldn't test this out in this pr but the testing you provided looks amazing! thank you!
john-rock
approved these changes
Nov 3, 2023
|
Will go ahead and merge this. If all works as expected a crawl should be triggered after this production build is complete! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What are you changing in this pull request and why?
Asana task
Adds Git workflow to trigger an Algolia crawl on PR merges.
To trigger the crawler, add the
trigger-crawllabel to a PR. Once the PR is merged, the GitHub Action will:trigger-crawllabel is setExample run from this PR
Web Team Testing
To test:
trigger-crawllabel set.Notes
Rather than using the
sleep 480command to wait 8 minutes before triggering the crawl, I looked into using this git action to watch for a Vercel deployment. However, this watches for preview deploys, so if a previous deploy preview was built from an earlier commit, this step will complete instantly and will allow the crawl to start before the live docs site is rebuilt.There's another git action for watching Vercel deployments. However their section on dynamically resolving a deployment URL has an example workflow which i'd rather not do due to the complexity of it.