Rebuild the site after the index, so a merged project opens on the web - #3
Merged
Merged
Conversation
…ithin minutes Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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
1 participant
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.
A project's web page at
superproto.dev/p/<id>/<name>is written by the canvas's Cloudflare Pages build, which runs on a push to super-prototyping. Until now a project merged here was listed on the community page at once, but its Open went to a 404 until the next push there.This adds one step to the Index workflow: it POSTs the Pages project's deploy hook, kept in the
PAGES_DEPLOY_HOOKsecret (already set). The page then exists a few minutes after the merge.🤖 Generated with Claude Code