status badges on README are broken
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- github-actions, python
- Domain
- ci-cd, documentation
Research direction
Start with the README badges and the .travis configuration directory named in the issue; inspect the repository’s existing GitHub workflows for the build and test badge targets. Replace the Travis-CI badges with the corresponding workflow badges and remove the obsolete configuration directory. Done when the README uses GitHub workflow badges and the .travis directory is gone.
Written by the indexing model from the issue text.
Description
Sasmodels in no longer using Travis-CI.
Replace the Travis-CI build and test status badges with the github workflow equivalents and remove the .travis configuration directory.
- Dominant language
- Python
- Stars
- 23
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from SasView/sasmodels
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
SasModels Infrastructure SasView coordination
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Documentation SasModels Infrastructure
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 3/5 Half a day Newbie friendliness 35/100
All issues in SasView/sasmodels
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Validate finite output clamping limits in StepPredictor.prepare_clamping_params to prevent silent NaN/Inf propagationPossibly taken @muskan-creates352 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
mllam/neural-lam#848 ·
Maintainers usually reply within 2 days
-
infra
Difficulty 1/5 Under an hour Newbie friendliness 88/100
fab-geocommuns/RNB-coeur#1166 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
deepspeedai/DeepSpeed#8951 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
aws/context-ontology-accelerator#343 ·
Maintainers usually reply within 1 day