marigold-dev / marigold-dev/deku
define how we should do esy lock updates
Open
Nobody has claimed this yet.
backlog
help wanted
- Dominant language
- OCaml
- Stars
- 82
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Ideally we should evaluate every dependency minor change during dependency updates, is that possible? If so when should we start to do? Also how?
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
The issue names no files, tests, or entry points. First clarify how esy lock updates currently happen, then determine whether each dependency minor change should be evaluated, when that evaluation should begin, and what process would define completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100