django-commons / django-commons/controls
Define test suite configuration for best-practices and repos
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- Avg merge
- 18m
- Merged PRs (30d)
- 1
Description
- Python and Django version matrixes
- GitHub actions integration
- Database configurations
- Running test suite locally
- Speed optimizations with uv and caching
I think the goal here is for clarity and long-term maintenance. We should try to stick to known technologies or popular things. If something is newer, it should be a minor difference compared to the alternatives (uv compared to poetry).
It feels like the decisions are around:
- Whether or not to use tox, nox or something else
- Which dependency manager for the github action to use
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by resolving the configuration decisions listed in the issue: the Python and Django version matrixes, GitHub Actions integration, database configurations, local test running, and caching or uv optimizations. Compare tox, nox, and dependency-manager options, then document a consistent setup whose choices support clarity, maintenance, and the stated test-suite requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, github-actions, python
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100