fix(cli): fix write-heading-ids CLI when no files provided#11763
Merged
fix(cli): fix write-heading-ids CLI when no files provided#11763
write-heading-ids CLI when no files provided#11763Conversation
✅ [V2]
To edit notification comments on pull requests, go to your Netlify project configuration. |
slorber
changed the title
write-heading-ids CLI when no files providedwrite-heading-ids CLI when no files provided
|
Size Change: +275 B (0%) Total Size: 11.9 MB ℹ️ View Unchanged
|
⚡️ Lighthouse report for the deploy preview of this PR
|
|
Size Change: +265 B (0%) Total Size: 12.3 MB ℹ️ View Unchanged
|
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.
Motivation
The CLI is supposed to find the md/mdx files to apply heading ids automatically, without having to provide files/patterns as CLI options.
Test Plan
local
Related issues/PRs
This feature broke in 2022 (#7583). Apparently, nobody complained so far 😅, but still, let's fix it.