Skip to content

Update guide to mention correct subdirectory #35556

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 28, 2021
Merged

Update guide to mention correct subdirectory #35556

merged 1 commit into from
Jan 28, 2021

Conversation

brentleyjones
Copy link
Contributor

@brentleyjones brentleyjones commented Jan 22, 2021

The guide as written results in lots of repositories being placed as siblings to swift-project, instead of inside of it. This also results in the build directory being a sibling. Changing the clone to the swift directory fixes this.

The guide as written results in lots of repositories being placed as siblings to `swift-project`, instead of inside of it. This also results in the `build` directory being a sibling. Changing the clone to the `swift` directory fixes this.
@@ -68,15 +68,17 @@ toolchain as a one-off, there are a couple of differences:
If you plan on contributing regularly, cloning over SSH provides a better
experience. After you've [uploaded your SSH keys to GitHub][]:
```sh
git clone [email protected]:apple/swift.git .
git clone [email protected]:apple/swift.git swift
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The dot may be superfluous but it's not incorrect. I would leave it in.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The dot is what makes it incorrect. Unless we change to the swift directory first.

@CodaFi
Copy link
Contributor

CodaFi commented Jan 23, 2021

Just one nit. Thanks!

@varungandhi-apple
Copy link
Contributor

varungandhi-apple commented Jan 24, 2021

Should we instead revert 565385b? It seems like that PR and this PR are both changing the same thing. 🤔

@brentleyjones
Copy link
Contributor Author

Yes, it seems 565385b is what broke it.

@varungandhi-apple
Copy link
Contributor

Since this is a very small change, I think it's okay if we merge this instead of creating another PR to revert 565385b, it doesn't really matter. [Sorry about the delay.]

@swift-ci smoke test and merge

@swift-ci swift-ci merged commit fcc6e88 into swiftlang:main Jan 28, 2021
@brentleyjones brentleyjones deleted the bj/update-guide branch January 28, 2021 13:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants