Repository navigation
Conversation
This file contains hidden or 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
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.
After a release tag, this workflow asks nanostores.net to rebuild its docs
from that tag. It is skipped until the notifier App is set up.
Part of nanostores/nanostores.net#15,
which builds the docs from release tags.
Enable it (once, by an org owner)
nanostores-site-notifierApp:guide.
→ New organization secret
SITE_NOTIFIER_KEY: the App's.pemfile. Repository access: the repositories above.
→ New organization variable
SITE_NOTIFIER_CLIENT_ID: the App'sClient ID, same repositories.
The job runs on the next release tag. Until then nanostores.net picks up
releases once a day.