ci: add merge-blocking markdown format check - #109
Merged
Merged
Conversation
Part of standardizing markdown formatting across the personal repos. This repo's markdown is already byte-identical to the standard, so this PR adds configuration only and changes no markdown whatsoever. - `.prettierrc.json` encodes the `mdf` standard (prose wrap at 80). Scoped to `**/*.md` via `overrides` so a stray `prettier --write .` cannot touch `pubspec.yaml` or workflow YAML. `embeddedLanguageFormatting: off` stops prettier rewriting fenced json/yaml examples. - `.prettierignore` excludes generated dartdoc output, which is untracked but would otherwise be caught by prettier's filesystem glob and make local runs disagree with CI. - `markdown.yml` pins prettier to the same version `mise` installs locally, and pins actions by SHA. The job is named `markdown` because the job ID becomes the check-run context that the branch ruleset matches on. The check is added to the ruleset only after this lands, so no in-flight PR is stranded by a required context that no workflow yet produces. No version bump or changelog entry: this changes CI configuration only and nothing in any published package.
📦 Dependency Lower-Bound Validation Summary✅
|
| Dependency | Declared Constraint | Declared Floor | Resolved Version | Status |
|---|---|---|---|---|
path |
^1.8.0 |
1.8.0 |
1.8.0 |
Exact Floor |
string_scanner |
^1.4.1 |
1.4.1 |
1.4.1 |
Exact Floor |
📊 Cognitive Complexity AnalysisNet Delta: 0 | Added: 0 | Increased: 0 | Improved: 0 | Violations: 0 No modified Dart declarations detected. |
The doc/api exclusion was speculative -- dartdoc output is never generated into these repos, so the file only added noise to the canonical set.
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.
Part of standardizing markdown formatting across the personal repos. This
repo's markdown is already byte-identical to the standard, so this PR adds
configuration only and changes no markdown whatsoever.
.prettierrc.jsonencodes themdfstandard (prose wrap at 80). Scoped to**/*.mdviaoverridesso a strayprettier --write .cannot touchpubspec.yamlor workflow YAML.embeddedLanguageFormatting: offstopsprettier rewriting fenced json/yaml examples.
markdown.ymlpins prettier to the same versionmiseinstalls locally, andpins actions by SHA.
The job is named
markdownbecause the job ID becomes the check-run contextthat the branch ruleset matches on. The check is added to the ruleset only
after this lands, so no in-flight PR is stranded by a required context that no
workflow yet produces.
No version bump or changelog entry: this changes CI configuration only and
nothing in any published package.