staged github actions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 3
- Avg merge
- 19h 43m
- Merged PRs (30d)
- 1
Description
currently we have 5 Github actions, I believe all of them run poetry install in order to create their virtual environment before executing their action. This feels like a waste of computation resources, we should instead have a single action which installs the 60+ packages needed for Dynode, then passes the env state to the other actions so they execute in parallel but without running the exact same installs multiple times.
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
Review the repository's five GitHub Actions workflows and locate each poetry install step. Determine how one dependency-install step could be reused while allowing the other actions to run in parallel; done means the workflows avoid repeating the same installation and still execute their existing actions successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100