mphowardlab / mphowardlab/lammpsio
Use bump version for releases
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 16
- Forks
- 3
- Avg merge
- 32m
- Merged PRs (30d)
- 2
Description
Now that we have docs to build, there is more than one place the version is specified. We should use bumpversion to make sure it all stays synced.
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
No files or tests are named. Start by locating every version declaration and the documentation build and release configuration; then determine how bumpversion should update them together. Done means releases use bumpversion and all version references stay synchronized.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100