django-commons / django-commons/controls
Define package versioning and releases to support test releases for best practices repo
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- Avg merge
- 18m
- Merged PRs (30d)
- 1
Description
Currently the best practices repo uses semvar with an environment variable for dev versioning to support uploads to testpypi.
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 reading src/django_commons_best_practices/init.py and .github/workflows/test_release.yml to understand the current environment-variable versioning and TestPyPI upload flow. Define the package versioning and release approach, including support for test releases, and verify that the documented workflow is consistent with the repository configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100