Note
This file is maintained by the foundry-python template and will be updated when you run mise run update_from_template.
Cause: Required services not configured.
Solution: Complete all sections in docs/foundry/getting-started.md.
Cause: Repository secrets not configured.
Solution: Add required secrets at https://github.com/aignostics/foundry-python-core/settings/secrets/actions:
GCP_WORKLOAD_IDENTITY_PROVIDERSONAR_TOKEN
Cause: Tests missing category marker.
Solution: Add @pytest.mark.unit, @pytest.mark.integration, or @pytest.mark.e2e to each test.
Cause: Code doesn't meet quality standards.
Solution: Many hooks auto-fix issues. Re-stage files and commit:
git add <fixed-files>
git commitCause: New code not covered by tests.
Solution: Add tests for new code, or verify new tests have category markers.
Cause: Message doesn't follow conventional commit format.
Solution: Use format type(scope): description. Valid types: feat, fix, docs, chore, refactor, test, perf, ci.
Cause: A dependency update introduced a breaking change.
Solution:
- Check which package was updated in the Renovate PR description
- Review the package changelog for breaking changes
- Fix the compatibility issue in a commit on the Renovate branch (Renovate branches accept external commits)
- If the fix is complex, close the Renovate PR and pin the dependency version in
pyproject.tomluntil you can address it
- README.md - Project documentation
- CODE_STYLE.md - Code style guide
- SECURITY.md - Security policy
- CONTRIBUTING.md - Contribution guidelines
Happy to hear from you if you have any feedback on the DX/UX of using foundry-python.
Please reach out on Slack.