Make workflow run on a cron #13723
Merged
Make workflow run on a cron #13723
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
LizBaker
requested review from
clarkmcadoo and
tabathadelane
and removed request for
a team
|
Hi @LizBaker 👋 Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days. Gatsby Cloud will automatically generate a preview of your request, and will comment with a link when the preview is ready (usually 20 to 30 minutes). |
jeff-colucci
added
the
eng
roadlittledawn
approved these changes
Jun 27, 2023
✅ docs-website-develop deploy preview ready
|
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.
the release notes workflow runs on merge to main which results in the json being immediately updated and builds taking up to 40min. this means in the product a release note can show up with a link to a docs page that hasn't gone live yet. this makes the workflow run around 7pm pdt which should be well after the last release of the day and hopefully avoid any more temporary 404s