`skip checkup` should test an Android build without Skip
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 3.2k
- Forks
- 106
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 1
Description
skip checkup initializes a fresh Skip app project and runs its build.
But, if we're running a checkup, then it's probably because we're unsure whether we can run any Android build.
skip checkup should generate a very basic Android project with no Skip in it at all, and verify that it builds without error. If that fails, there's no point in running a full-blown Skip project.
Failure in that step would narrow down the scope of the problem to just the user's Android SDK.
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
Start at the skip checkup command and trace how it currently creates and builds the fresh Skip app. Make done mean that a minimal Android project with no Skip dependency builds successfully before the full Skip checkup runs, and that a failure identifies the Android SDK as the likely scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, swift
- Domain
- build-system, mobile-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 52/100