Conversation
…1% not 92%) Fix integration snapshot description — snapshot is committed, not gitignored.
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
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.
Pull Request
Summary
CONTRIBUTING.mdclaimed a 92% coverage requirement but the enforced threshold inpackages/parser-core/pyproject.toml(fail_under = 91) and.github/PULL_REQUEST_TEMPLATE.mdboth say 91%. Aligns all three sources. Also corrects the integration snapshot description — the snapshot is committed to the repo (no personal data), not gitignored.Changes
CONTRIBUTING.md: replace all92%→91%(5 occurrences: verify step, workflow step, coverage section, PR checklist, CI checks list)CONTRIBUTING.md: fix integration snapshot description to reflect committed baselineType
Testing
Checklist
Downstream impact
bankstatements_core(exported class, function, or exception)