Ensure that the .swift-version file exists before calling swiftly use
#1875
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
matthewbastien
requested review from
0xTim,
adam-fowler and
award999
as code owners
matthewbastien
force-pushed
the
swiftly-use
branch
from
e29a138 to
f45e69c
Compare
Member
Author
|
Unrelated test failure. Merging. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Some instances of Swiftly do not actually create the
.swift-versionfile whenswiftly useis called. They will only modify an existing.swift-versionfile. This is definitely an issue with Swiftly itself, but we can at least mitigate the problem in the Swift extension until we can determine a proper fix.Tasks
[ ] Documentation has been updated[ ] Added an entry to CHANGELOG.md if applicable