ocaml-dune / ocaml-dune/binary-distribution
Keep the database where the releases are
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 4
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
Currently the database of releases, metadata.json is in the repo. This presents a number of issues:
- It has no relation to what binaries are actually available to be served, e.g. when using the
stagingbranch themetadata.jsonis the same, but the location for binaries is different, thus the configuration in total is incorrect - It requires the workflows to commit to the repo, thus over time creating tons of commits and potential merge conflicts.
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 by reading metadata.json and the release workflows that currently commit it, then compare how the staging branch locates its binaries. Done should mean release metadata matches the binaries actually served for each branch and workflows no longer create repository commits for metadata updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- devops, release
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100