Improve validate-mdx and calibre actions#2571
Merged
mdlinville merged 2 commits intomainfrom Apr 28, 2026
Merged
Conversation
- Succeed early if the commit includes no eligible changes, bailing before trying to install the mint CLI - Better detection of the Git state in the PR
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Use repo secret that contains a classic PAT with with read-write access to wandb/docs so that the action can add a commit to a PR that adds or updates images
2c0e950 to
a4a018f
Compare
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.
Description
validate-mdxhanging when a commit changes no MDX files, like when the Calibre action runs. Now:mintCLI. formint validateto consider, like when the Calibre action commits an image optimization.(mdx|json|ya?ml|png|jpe?g|webp)GITHUB_TOKENto write into a PR if the image is added / updated by a commit after the first one. I created a classic PAT owned bywandbthat grants read-write access only towandb/docs, saved it as a repo secret, and updated the action to use it. We were confused why this seemed to not be a problem forcoreweave/docsbut I was actually able to reproduce it by the second commit in https://github.com/coreweave/docs/pull/2949. CoreWeave won't be able to use a PAT but could potentially use the same auth mechanism that is approved for DocEngine.Testing
mint dev)mint broken-links)