Hompage Quick Start: clarify when/where to run git lfs install
#37
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
Previous instructions are vague on where the command should be run (eg it needs to be *in* the repo directory so it can install hooks) and misleading in that it suggests you only need to set up Git LFS once. What it means to say is that you only need to set it up once, _per repository_ as the relevant hooks need to be installed per-repo. This clarifies both points and fixes a minor display issue where the Download link actually incorporates the whitespace after the word "Download".
ttaylorr
approved these changes
Feb 1, 2019
Contributor
|
This looks great; thanks! |
chrisd8088
added a commit
that referenced
this pull request
Feb 21, 2020
We further clarify the documentation on the home page regarding how and when to install and configure LFS, distinguishing the normal one-time (per user) install step from the per-repository tracking setup steps, and also noting the "git lfs migrate" command and its use in dealing with pre-existing files. This builds on the clarifications added in PR #37 (commit 3eb274c).
chrisd8088
added a commit
that referenced
this pull request
Feb 21, 2020
We further clarify the documentation on the home page regarding how and when to install and configure LFS, distinguishing the normal one-time (per user) install step from the per-repository tracking setup steps, and also noting the "git lfs migrate" command and its use in dealing with pre-existing files. This builds on the clarifications added in PR #37 (commit 3eb274c).
chrisd8088
added a commit
that referenced
this pull request
Feb 21, 2020
We further clarify the documentation on the home page regarding how and when to install and configure LFS, distinguishing the normal one-time (per user) install step from the per-repository tracking setup steps, and also noting the "git lfs migrate" command and its use in dealing with pre-existing files. This builds on the clarifications added in PR #37 (commit 3eb274c).
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.
Previous installation instructions are vague on where the command should be run (eg it needs to be in the repo directory so it can install hooks) and misleading in that it suggests you only need to set up Git LFS once. What it means to say is that you only need to set it up once, per repository as the relevant hooks need to be installed globally and per-repo.
This clarifies both points and fixes a tiny display issue where the Download link actually incorporates the whitespace after the word "Download".