Publish the browser probe to GitHub Pages - #21
Merged
Conversation
The page was already in the repo but only runnable by cloning it, which is most of the reason a CLI in a repo goes unseen in the first place. Deploys web/ as-is — one static file, no build step. Fires only when the page actually changes: a Rust-only commit has nothing to republish, and a deploy on every push would make the deploy history useless for asking when the page last changed. Concurrency is set not to cancel in flight, since a half-published page is worse than a slightly stale one. Co-Authored-By: Claude Opus 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
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.
The page was already in the repo but only runnable by cloning it — which is most of the reason a CLI in a repo goes unseen in the first place.
Deploys
web/as-is: one static file, no build step, no toolchain.Two deliberate settings:
web/or the workflow itself changes. A Rust-only commit has nothing to republish, and deploying on every push would make the deploy history useless for answering "when did the page last change?"cancel-in-progress: false. A half-published page is worse than a slightly stale one.Pages is already enabled on the repo with
build_type: workflow. The site lands at https://emilbob.github.io/substrate-node-probe/ — the repo is public, so nothing here exposes anything that wasn't already readable.🤖 Generated with Claude Code