CI: consider caching pip downloads in tests.yml
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.2k
- Forks
- 726
- Avg merge
- 11d 11h
- Merged PRs (30d)
- 7
Description
There are five workflows that use the `actions/setup-python` action and run `pip install` but don't enable pip caching. Each workflow run downloads all deps from PyPI even when `requirements.txt` hasn't changed. Especially in `tests.yml` which spawns 12+ matrix runners per PR, I think we can reduce CI time.
```yml
- uses: actions/setup-python@v5.0.0
with:
python-version: "3.13"
cache: 'pip'
```
Contributor guide
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
Inspect tests.yml first, then locate the other four workflows that use actions/setup-python and run pip install. Compare their dependency files and existing setup-python configuration, then enable pip caching where appropriate. Done means the workflows use the requested cache and CI completes successfully with the existing test matrix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100