xcodes should automatically update if it failed to find the provided version
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Swift
- Stars
- 4.8k
- Forks
- 182
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 1
Description
A common flow is:
- Oh! A new Xcode 12.0.1 has been released
- Open Terminal
$ xcodes install 12.0.1
Could not find version 12.0.1.
😔
$ xcodes update && xcodes install 12.0.1
(1/6) Downloading Xcode 12.0.1: 5%
...
Instead, it should work like:
- Oh! A new Xcode 12.0.1 has been released
- Open Terminal
$ xcodes install 12.0.1
Could not find version 12.0.1, but will update in case it's a recent release.
Updating...
(1/6) Downloading Xcode 12.0.1: 5%
...
It's still possible to fail, which would look like:
$ xcodes install 25.2
Could not find version 25.2, but will update in case it's a recent release.
Updating...
Could not find version 25.2.
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 xcodes install command's version lookup and its existing update flow. Reproduce the documented install attempts for 12.0.1 and an unavailable version such as 25.2. Done means install retries after a failed lookup, reports the update, and still shows a final not-found result when updating does not help.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100