Feat/add ci quality gates#223
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Summary
Adds CI quality gates for formatting, linting, migrations, tests, and coverage through GitHub Actions.
Changes
pyproject.tomlcoverage.xmlpyproject.tomlpytest.iniand.coveragercin favor of one shared project configBehavior
CI now runs the same validation flow on every push and pull request. The workflow installs dependencies, starts PostgreSQL, runs migrations, checks Ruff and Black, then runs pytest using the repository’s shared test and coverage configuration.
Why
This creates a consistent quality gate for branch updates and PRs while reducing configuration drift between local development and GitHub Actions. It also fixes the previous formatter/config precedence issue caused by overlapping config files and incomplete Black exclusions.
Validation
The workflow is configured to run:
python manage.py migrateruff check .black --check .pytest -qPytest coverage policy is now sourced from
pyproject.toml, including XML output and the minimum coverage threshold.Result
The repository now has a single source of truth for test and coverage behavior, and CI enforces formatting, linting, migrations, tests, and coverage consistently.
Notes
pyproject.tomlnow owns pytest and coverage configurationpytest.iniand.coveragercwere removed to prevent config precedence conflictsCODECOV_TOKENsecret