chore: format the mu-Ziq remediation plan - #2390
Merged
Merged
Conversation
`plans/mu-ziq-replacement-char-remediation.md` landed unformatted and fails `npm run format:check`, which is a required check on every PR but does not run on pushes to main — so the break went unnoticed and now blocks unrelated PRs. Every other file under `plans/` is prettier-clean; this restores that. Content is untouched apart from Prettier's own rewrites: emphasis markers normalize from `*x*` to `_x_`, and the `yaml` fence showing the `test.yml` paths-filter addition loses the leading indentation that placed it at its nesting level in that file. If that indentation was load-bearing for the reader, re-fence the block as `text` so Prettier leaves it alone.
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.
plans/mu-ziq-replacement-char-remediation.mdlanded unformatted ina5b9ebec/9494e314and failsnpm run format:check. That check is required on every PR but does not run on pushes tomain, so the break went unnoticed and is now failinglint-and-typecheckon unrelated PRs (#2389 hit it). Every other file underplans/is prettier-clean; this restores that.Formatting only — no content edits. Two things Prettier rewrote that are worth a look:
*x*to_x_(repo-wide house style; every sibling plan already uses_).yaml fence showing the `test.yml` paths-filter addition loses the leading indentation that had placed it at its real nesting level in that file. If that was load-bearing for the reader, re-fence it astext and Prettier will leave it alone.Testing
npx prettier --check .is clean on this branch.