neume-network / neume-network/data
In this repository, it can be that in the results directory we publish JSON objects that aren't compliant with @neume-network/schema
Open
Nobody has claimed this yet.
bug
- Dominant language
- JavaScript
- Stars
- 15
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
- We should have a GitHub Actions test that periodically checks whether we're compliant with our own schema
- Specifically for music-os-accumulator-extraction
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
Inspect results/music-os-accumulator-extraction and the repository's existing GitHub Actions configuration first. Check how @neume-network/schema can validate these published JSON objects, then add a periodic workflow check whose successful run confirms the results remain schema-compliant.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- ci-cd, data, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100