Create a `cache-project-venv` action
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 2
- Forks
- 0
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 1
Description
Problem to Solve
The caching logic in analyze-project would be useful for other workflows:
- It generates a cache key based on the project name in the pyproject.toml file, the Python version from setup-python, etc.
- It asks Poetry for the venv path instead of hardcoding it.
Proposed Solution
Extract the caching steps into a cache-project-venv action.
Add use-cache and cache-hit inputs/outputs for testing, like in setup-poetry.
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
Start by locating the caching logic in the existing analyze-project action and compare setup-poetry's use-cache and cache-hit inputs and outputs. Extract the project-name, Python-version, and Poetry virtual-environment-path behavior into the new cache-project-venv action, then verify its cache controls and outputs in the relevant workflows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100