Skip to content

Commit 127e70e

Browse files
authored
Merge pull request #53 from sachinjoseph/main
Fix broken link
2 parents fad1a54 + ea72b95 commit 127e70e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

_includes/home/secondary.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ <h2 class="section-heading">Getting Started</h2>
2626
<pre>git lfs track "*.psd"</pre>
2727
<p>Now make sure .gitattributes is tracked:</p>
2828
<pre>git add .gitattributes</pre>
29-
<p>Note that defining the file types Git LFS should track will not, by itself, convert any pre-existing files to Git LFS, such as files on other branches or in your prior commit history. To do that, use the <a href="https://github.com/git-lfs/git-lfs/blob/main/docs/man/git-lfs-migrate.1.ronn?utm_source=gitlfs_site&amp;utm_medium=doc_man_migrate_link&amp;utm_campaign=gitlfs">git lfs migrate[1]</a> command, which has a range of options designed to suit various potential use cases.</p>
29+
<p>Note that defining the file types Git LFS should track will not, by itself, convert any pre-existing files to Git LFS, such as files on other branches or in your prior commit history. To do that, use the <a href="https://github.com/git-lfs/git-lfs/blob/main/docs/man/git-lfs-migrate.adoc?utm_source=gitlfs_site&amp;utm_medium=doc_man_migrate_link&amp;utm_campaign=gitlfs">git lfs migrate(1)</a> command, which has a range of options designed to suit various potential use cases.</p>
3030
</li>
3131
<li>
3232
<p>There is no step three. Just commit and push to GitHub as you normally would; for instance, if your current branch is named <code>main</code>:</p>

0 commit comments

Comments
 (0)