Repository navigation
Deploy only from GitHub's main, through mise run deploy - #8
Merged
Merged
Conversation
mise run deploy now guards, checks, pushes, waits for Cloudflare Pages and verifies. deploy-status says whether main is live. verify fails on any failing line, not just the last. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Deploying landnav-website with
|
| Latest commit: |
b602abd
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://1b64acf2.landnav-website.pages.dev |
| Branch Preview URL: | https://deploy-guard.landnav-website.pages.dev |
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.
mise run deployis now the only way this site ships. The push is the deploy, so it runsscripts/deploy-guard.sh --allow-ahead, thencheck, then the guard again, thengit push origin main. It then waits for the "Cloudflare Pages" check run on the commit (scripts/pages-status.sh --wait, up to 10 minutes) and runsverify. The guard refuses unless the branch ismain, the tree is clean (untracked files too) andorigin/mainisn't ahead. A localmainthat is ahead is allowed.mise run deploy-statusreads the same check run and says whethermainis live.verifynow hasset -e. Before, a multi-line mise task only failed if its last line failed, so a broken home page passed as long as the 404 check did.scriptsis in_config.yml'sexclude, so Jekyll doesn't publish it./scripts/deploy-guard.shis a 404 on the live site.mise run deploy" and link Workshop's deploy note.Refusals
Tested on merged
mainin a scratch clone whose origin is a local mirror, so nothing could reach GitHub or Cloudflare:After the merge,
deploy-statussaidorigin/main (0f85684) is live.andverifypassed. Nomise run deploywas run for real here.🤖 Generated with Claude Code