Commit 385d1849 authored by Marcia Ramos's avatar Marcia Ramos Committed by Achilleas Pipinellis

Axil's review

parent dda62dd1
# Migration Guide from Git Annex to Git LFS # Migration Guide from Git Annex to Git LFS
> Type: user guide
>
> Level: beginner
> GitLab EE is deprecating > GitLab EE is deprecating
[support to **git-annex**][post-intro-annex] from version [support to **git-annex**][post-intro-annex] from version
8.17 on (released on 2017/02/22). It 8.17 on (released on 2017/02/22). It
...@@ -20,17 +24,14 @@ in your [local environment][install-annex-local]. ...@@ -20,17 +24,14 @@ in your [local environment][install-annex-local].
On GitLab.com, **git-annex** was enabled, and you had On GitLab.com, **git-annex** was enabled, and you had
only to install it locally. only to install it locally.
### TL;DR ### TL; DR
> We assumeyou have [git-annex enabled](#enabling-annex) in your repository.
If you want to skip the reading and go straight to the point, If you want to skip the reading and go straight to the point,
this is what you need to do: this is what you need to do:
```bash ```bash
# Enable git-annex (what we expect you to have done so far)
$ git annex init
$ git annex add <files>
$ git commit -m "commit message"
$ git annex sync --content
# Disable git-annex # Disable git-annex
$ git annex direct $ git annex direct
$ git annex uninit $ git annex uninit
...@@ -183,7 +184,7 @@ To keep your repo clean, let's remove all ...@@ -183,7 +184,7 @@ To keep your repo clean, let's remove all
Git LFS is enabled by default on all GitLab products Git LFS is enabled by default on all GitLab products
(GitLab CE, GitLab EE, GitLab.com), therefore, you (GitLab CE, GitLab EE, GitLab.com), therefore, you
don't need to do anything in the server side. don't need to do anything in the server-side.
First, let's make sure you have **git-lfs** installed First, let's make sure you have **git-lfs** installed
locally: locally:
...@@ -193,11 +194,7 @@ $ git lfs help ...@@ -193,11 +194,7 @@ $ git lfs help
``` ```
If the terminal doesn't prompt you with a full response If the terminal doesn't prompt you with a full response
on **git-lfs** commands, [install LFS][install-lfs] first: on **git-lfs** commands, [install LFS][install-lfs] first.
```bash
$ brew install git-lfs
```
[Enable **git-lfs**][lfs-track] for the group of files you [Enable **git-lfs**][lfs-track] for the group of files you
want to track with it. You can track specific files, all want to track with it. You can track specific files, all
...@@ -235,7 +232,7 @@ Once you do that, run `git status` and you'll see ...@@ -235,7 +232,7 @@ Once you do that, run `git status` and you'll see
file patterns that you chose to track via **git-lfs**. file patterns that you chose to track via **git-lfs**.
To see **git-lfs** working, look at the project's size (in To see **git-lfs** working, look at the project's size (in
bites), update one of your files, and push a change bytes), update one of your files, and push a change
to the remote. to the remote.
- Repo size: 492 KB - Repo size: 492 KB
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment