[codex] Skip Pages deployment outside upstream#4
Merged
Conversation
The LDMB123 fork does not have a GitHub Pages site configured, so the upstream docs deployment workflow fails on pushes with a Pages 404 even though CrabBox CI and runtime checks are healthy. Limit the deploy job to openclaw/crabbox so upstream deployment behavior is preserved and fork syncs do not report a false Pages failure.
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.
Summary
openclaw/crabbox.Verification
ruby -e "require 'yaml'; YAML.load_file('.github/workflows/pages.yml'); puts 'yaml ok'"Context: PR #3 merged cleanly and CI passed, but the post-merge Pages workflow failed with a Pages 404 because this fork has no GitHub Pages site configured. This change preserves upstream deployment behavior while keeping the fork's push checks clean.