OpenAstronomy / OpenAstronomy/github-actions-workflows
Document or Improve the way to force the workflow to install a specific tox version.
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 21
- Forks
- 27
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 1
Description
tox 4.0.0 came out and things broke. Do you test against dev or pre-release version of tox?
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 reviewing the reusable GitHub Actions workflows and how they install tox, then compare the tox 4.0.0 breakage with the linked tox issue. Done means the supported way to force a specific tox version is documented or improved, and the project's testing of development or pre-release tox versions is clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, tooling
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100