Repository navigation
Commit Help Center snapshots only after a successful deploy - #1
Merged
Merged
Conversation
…epo, Actions and Pages status help.yml committed the version snapshot to help-versions before deploying, so a failed deploy (Pages unavailable, an outage) still used up a version number. The snapshot is now committed after deploy-pages succeeds. PREREQUISITES.md: the repo now exists (private); Actions jobs aren't started because of the org's billing; Pages isn't available for this private repo on the current plan. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Adron
commented
Oct 23, 2026
Adron
left a comment
Adron
left a comment
Member
Author
There was a problem hiding this comment.
Reviewed.
- help.yml: steps are now build → configure-pages → upload → deploy → commit snapshot. A failed deploy ends the job before the archive commit, so no version number is used up. The live site still carries the new snapshot, because help-build.rb copies it into _site/versions/ before deploying.
- Edge case: if deploy succeeds and the snapshot push then fails, the next run reuses that version number and replaces it on the live site. Acceptable: the help-pages concurrency group runs releases one at a time, so there's no race.
- PREREQUISITES.md matches what GitHub returned: the repo is private, Actions billing errors, and Pages returns 422 on this plan.
- Local checks pass (workflow YAML, 15 tests, Help Center build + link check). CI can't start until billing is fixed.
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.
What
help.yml: the version snapshot is committed tohelp-versionsonly afterdeploy-pagessucceeds. Before this change, it was committed first, so a failed deploy still used up a version number in the archive. Pages is currently unavailable for this repo, so that would have happened on the first run.docs/PREREQUISITES.md: records the repo's real state after the first push:422)Verification
CI can't run until the Actions billing is fixed, so I checked locally:
help.ymlstep order is now build → configure-pages → upload → deploy → commit snapshot.swift testinPackages/SubstratalKit: 15 tests pass.help-generate+jekyll build+help-check: 75 screen pages, 115 internal links, none broken.🤖 Generated with Claude Code