Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: display parsing errors as violations #299

Merged
merged 18 commits into from
Feb 28, 2021
Merged

fix: display parsing errors as violations #299

merged 18 commits into from
Feb 28, 2021

Conversation

andreoliwa
Copy link
Owner

Fixes #296

@andreoliwa andreoliwa self-assigned this Feb 26, 2021
@andreoliwa andreoliwa changed the title Deal with ParsingError (fix, warn about it or ignore it) fix: display parsing errors as violations Feb 27, 2021
ci: move config to .bumpversion.cfg to avoid removing comments
@andreoliwa andreoliwa merged commit 4e189eb into develop Feb 28, 2021
@andreoliwa andreoliwa deleted the parsing-error branch February 28, 2021 17:07
github-actions bot pushed a commit that referenced this pull request Feb 28, 2021
## [0.24.1](v0.24.0...v0.24.1) (2021-02-28)

### Bug Fixes

* display parsing errors as violations ([#299](#299)) ([4e189eb](4e189eb))
@github-actions
Copy link

🎉 This PR is included in version 0.24.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions github-actions bot added the released Feature/fix is released label Feb 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
released Feature/fix is released
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

nitpick@0.24 fails with ParsingError
1 participant