Materials-Consortia / Materials-Consortia/optimade-python-tools
Create CI job to test `mike`
Open
Nobody has claimed this yet.
CI
priority/low
tests
- Dominant language
- Python
- Stars
- 91
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
Description
From a comment by @ml-evs it might be good with some testing of mike - especially considering consistency and updating the package.
This could be done via a CI job that runs mike deploy to a local branch.
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
No files or tests are named. Start by reviewing the repository's existing CI configuration and the package/update workflow, then determine how a CI job can run mike deploy against a local branch. Done means the job runs successfully and checks consistency while updating the package.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100