post about installation instructions, self-containedness, and auto-deployment via github
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1
- Forks
- 1
- Avg merge
- 15d 20h
- Merged PRs (30d)
- 1
Description
Run tests too, and put one of those test-coverage badge things on the project.
The main point though, is to make sure all of the input data files are known to git, so folks can actually download the software and run the simulations.
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
No files or tests are named. Start by inspecting the repository contents and existing installation, test, and GitHub configuration; identify the simulation input data and how tests currently run. Done means the required data is tracked, tests and coverage reporting are addressed, and the requested installation or auto-deployment setup is documented and reproducible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100