Open
Conversation
use https instead of git so that a GitHub account with SSH key is not required
specify desired directory in the clone command instead of using `cd`
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Previously, the README instructions would require a GitHub account setup with SSH to clone the repository. The only advantage I can see of doing things this way is if you had permissions to push updates to vubiostat/Renv. Using
https:allows anyone to clone this.I also removed
cdin favor of specifying the clone location at the end of theclonecommand: This has the advantage that it's one line instead of two, and it's more transparent (I believe more people are familiar with~than the fact thatcddefaults to taking you to your home directory).