Remove CI or move to Github Actions
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- ci-cd
Research direction
Start by inspecting the CircleCI configuration and the repository's build setup. Determine whether CI should be removed or moved to GitHub Actions; the work is done when the chosen approach is implemented and the build is no longer red.
Written by the indexing model from the issue text.
Description
The build is red right now because the CircleCI config has changed. Maybe we don't need CI since we don't have tests 🙈
- Dominant language
- Kotlin
- Stars
- 5
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from getodk/counter
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nightscout/AndroidAPS#5621 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
confluentinc/intellij#683 ·
Maintainers usually reply within 9 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
theopenconversationkit/tock#2166 ·
Maintainers usually reply within 1 day
-
follow-up
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
navikt/innsending-api#531 ·
Maintainers usually reply within 2 days
-
bug CLI
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
rafaeltonholo/svg-to-compose#379 ·