fix(sync-docs): unfreeze the docs sync push and PR creation - #8
Merged
Conversation
|
🚅 Deployed to the website-pr-8 environment in rivet-website
|
railway-app
Bot
temporarily deployed
to
rivet-website / website-pr-8
August 18, 2026 22:51
Destroyed
railway-app
Bot
temporarily deployed
to
rivet-website / website-pr-8
August 18, 2026 22:54
Destroyed
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 docs sync has been failing on every run since the first sync PR merged. Two independent causes:
--force-with-leaseagainst a branch this shallow checkout never fetched, so the lease had no baseline and the push was rejected as stale on every run after the branch first existed. The branch is rebuilt from the product repo each run, so there is no prior state to protect.gh pr view <branch>, which also resolves closed and merged PRs. Once the first sync PR merged, the guard always matched it and no new PR was ever opened.Left
vendor/actorsstuck at thedocs/bundle move, 13 commits behind the product repo.