This repository was archived by the owner on Jun 1, 2023. It is now read-only.
-
Couldn't load subscription status.
- Fork 97
Add a Troubleshooting section to the README #286
Merged
mattt
merged 2 commits into
SwiftDocOrg:master
from
AngeloStavrow:add-troubleshooting-to-readme
Jun 1, 2021
Merged
Add a Troubleshooting section to the README #286
mattt
merged 2 commits into
SwiftDocOrg:master
from
AngeloStavrow:add-troubleshooting-to-readme
Jun 1, 2021
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
Move troubleshooting to installation section
Thanks so much for opening this PR, @AngeloStavrow! I did some copy-editing and moved the discussion to be closer to the Homebrew installation instructions with eded277. I'm really glad to have this information in the README, to help anyone else who hits the same issue.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Closes #283.
This PR adds a first entry to a new troubleshooting section in the README, addressing #211. Please let me know if you'd prefer a different format or language, and I'll adapt this!