ci: exclude generated changelog from formatting - #19
Merged
Conversation
f0rr0
marked this pull request as ready for review
July 28, 2026 00:57
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.
What changed
CHANGELOG.mdfrom Oxfmt through the existingignorePatternsconfiguration.Why
Release Please owns and regenerates the changelog. Its generated Markdown differs from Oxfmt's preferred formatting, which caused the automated 3.0.0 release PR to fail the
Checkjob even though the package code and release metadata were valid.Impact
Source, tests, documentation, package metadata, and workflow files remain formatting-checked. Only the bot-generated changelog is excluded, preventing future release PRs from failing on formatting churn.
Validation
bun run checkoxfmt --check CHANGELOG.mdconfirms the file is excluded by the configured ignore rule