Repository navigation
ci: fix formatting check and check only changed Markdown links on PRs - #16
Merged
Merged
Conversation
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.
Summary
npm run format:checkonmain. This is Prettier output only; the two Azure files now match upstream Portkey exactly.--files-from, so file names never pass through a shell. This needslychee-action@v2.9.0(lychee 0.24.2).--root-dirresolves root-relative links such as/cookbook/...; without it lychee 0.24 reports them as errors.Evidence
npm run format:checkpasses.README.md, scheduled run → all 30 Markdown files.README.md(offline): 7 errors without--root-dir, 0 with it. An empty list exits 0.Merge risk