`skip checkup` seems to require a running emulator

Open Beginner friendly
#14 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
65/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
android, kotlin
Domain
documentation

Research direction

Open the Getting Started page linked in the issue and review the skip checkup instructions. Verify the behavior with and without a running Android emulator, then document that the command can stall during Kotlin tests when no emulator is available. Done means the requirement is clearly visible to new users.

Written by the indexing model from the issue text.

Description

I can run skip checkup successfully, but only if an Android emulator is running. Otherwise, skip checkup gets stuck at Kotlin tests. Maybe this is obvious to most users, but it would be nice if that was mentioned in the Getting Started page.

Dominant language
MDX
Stars
32
Forks
8
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from skiptools/skip.dev

All issues in skiptools/skip.dev

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.