Notify superdb-website repo instead of zed-doc-site when docs change #5491
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.
This is related to other PRs:
When we're ready to make SuperDB docs available as part of https://superdb.org/ (i.e., soon), we can merge this PR so that when contents of
docs/
change and we want to publish an updated docs site, CI will now notify the superdb-website repo instead of the zed-docs-site repo.Since the triggering is done via Actions' repository dispatch events, we could merge this change even before there's any Workflow in the superdb-website repo listening for it and reacting to it, i.e., for now the event generated by CI would just go out into the ether, unclaimed. We wouldn't want to be in that state for long since it would mean tip-of-
main
SuperDB docs updates aren't being published anywhere. But it allows for some wiggle room in the timing of when we merge related PRs.