Repository navigation
Skip docs sync pushes when nothing changed - #9
Merged
Merged
Conversation
The nightly publish run re-renders from scratch; without this it force-pushed an identical tree every night, re-running docs CI and the Mintlify deploy on the sync PR for no change. Co-authored-by: openhands <openhands@all-hands.dev>
Docs preview✅ Docs preview is ready: https://allhandsai-cookbook-preview-pr-9.mintlify.site
Docs PR: OpenHands/docs#887 (draft preview; never merged, closes with this PR). |
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
2 participants
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.
Why
The nightly Docs publish run re-renders every page from scratch and committed and force-pushed the result even when it matched what was already on the
cookbook-syncbranch. That re-ran the docs repository's CI and the Mintlify deployment on the sync PR every night for no change.docs_sync.py pushnow compares the rendered tree with the existing branch and only pushes when they differ. Preview branches get the same check, so re-running a preview on an unchanged PR reuses the deployment that already exists.Validation
cookbook-preview/pr-9 already has these files; not pushing. The docs branch head was unchanged, and the run still reported the existing Mintlify preview.This PR was drafted by an AI agent on behalf of the user.
@jpshackelford can click here to continue refining the PR