Repository navigation
Let the agents' page be deployed by hand from main - #28
Merged
Merged
Conversation
Page-only merges skip CI, so Pages never runs for them. A manual Pages run now checks the page against the current latest release and deploys main, skipping if main has moved on before the deploy. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Page-only merges (like #25 and #27) skip CI, so Pages never runs for them and the agents' page isn't updated.
This adds a manual trigger to the Pages workflow:
gh workflow run Pages(or Run workflow on the Actions tab) deploysmain.main, and only deploy if their commit is still the head ofmain.tests/pages_deploy.mjscovers the manual guard: deploys at the head ofmain, skips oncemainmoves, and never deploys on an API failure.🤖 Generated with Claude Code