Should `package_test` be in a `tox` environment?
Open
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
The package test will run on CI: https://github.com/scipp/copier_template/blob/main/template/.github/workflows/test.yml#L56
It would be useful to be able to run it easily locally with 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 with template/.github/workflows/test.yml at the linked package-test step, then inspect the repository's existing tox configuration or entry points. Add a tox environment that runs the same package test locally, and verify that tox completes successfully with equivalent results.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100