Two alternatives:

(1) Using the GIT_LFS_SKIP_SMUDGE variable:

    GIT_LFS_SKIP_SMUDGE=1 git clone SERVER-REPOSITORY

Obs: for &quot;Windows&quot;, use the following two commands:   

    set GIT_LFS_SKIP_SMUDGE=1  
    git clone SERVER-REPOSITORY

(2) Configuring the git-lfs smudge:

    git config --global filter.lfs.smudge &quot;git-lfs smudge --skip -- %f&quot;
    git config --global filter.lfs.process &quot;git-lfs filter-process --skip&quot;
        
    git clone SERVER-REPOSITORY

To undo this configuration, execute:

    git config --global filter.lfs.smudge &quot;git-lfs smudge -- %f&quot;
    git config --global filter.lfs.process &quot;git-lfs filter-process&quot;










I&#39;m currently struggling myself to find a clean way to download (and remove afterwards) large files with git-lfs.

However, there is a third alternative to the post of @Marcelo &#193;vila de Oliveira:

`git lfs install --skip-smudge`

will define globally to skip lfs downloads initially, when cloning repositories.

---
&amp;#160;

**EDIT:**
I&#39;ve created a tutorial for basic git-lfs handling. Any feedback and suggestions are very welcome.

You can find it at:

https://sabicalija.github.io/git-lfs-intro/

or pull it via:

`git clone https://github.com/sabicalija/git-lfs-intro.git`

I have an array like this:

    [{name:&quot;test&quot;, time:&quot;Date 2017-02-03T08:38:04.449Z&quot;}]
I stored it in `localstorage` and when I retrieving data from `localstorage` I got the value:

    [object, object]

How can I solve this issue?

**config.ts**

    import { Injectable } from &quot;@angular/core&quot;;
    
    @Injectable()
    export class TokenManager {
    
      public tokenKey: string = &#39;app_token&#39;;
    
      constructor() { }    
    
      store(content) {
        var contentData;
    
        console.log(&quot;inside localstorsge store:&quot;, content);
        contentData = content.map(
          (data) =&gt; data.name
        )
        console.log(&quot;contentData:&quot;, contentData)
        localStorage.setItem(this.tokenKey, content);
      }
    
      retrieve() {
        console.log(&quot;inside localstorage&quot;);
        let storedToken: any = localStorage.getItem(this.tokenKey);
        console.log(&quot;storedToken:&quot;, storedToken);//====&gt; here this console is[object object]
        if (!storedToken) throw &#39;no token found&#39;;
        return storedToken;
      }
    
    }

Storing Objects in localStorage

I can see that Log facade is very useful.
In the docs of laravel:

&gt; The logger provides the eight logging levels defined in RFC 5424:
&gt; emergency, alert, critical, error, warning, notice, info and debug.

But, how would I log an instance of a model? like for example:

    $user= User::find($user_id);

then, would it be possible to log the `$user` object?



How to Log object?

Is there a way to explicitly ignore all git-lfs files on `clone` and `pull`?&lt;br&gt;(besides uninstalling `git-lfs` which I ended up doing).

----

In this case git-lfs just contains pre-compiled libs for a platform I don&#39;t use... so there is absolutely no use in getting them.

How to clone/pull a git repository, ignoring LFS?

Is there a way to explicitly ignore all git-lfs files on <code>clone</code> and <code>pull</code>? (besides uninstalling <code>git-lfs</code> which I ended up doing).
<hr>
In this case git-lfs just contains pre-compiled libs for a platform I don't use... so there is absolutely no use in getting them.

I am new to GIT, so far I had been using Visual Studio Online TFS for my version control and I am the **only** developer. When I created my last project I was kind of mislead into thinking GIT was the best option for this.

So I checked-in my master. Then when I was going to work on a Feature I read I had to create a branch (this was not necessary in TFS) so I created &quot;development_print&quot; as a new branch and worked on my feature.

Now my feature is complete but I don&#39;t know how to merge it back into master. I am not interested in multiple branches at the moment, just want my new feature merged into master and remain with master.

In VS there is a **merge branch** option but it only allows me to merge into development_print (I want my feature into master!) so it does not let me set Into Current Branch and for Merge From Branch shows: 

 - Development_print
 - master
 - origin/development_print
 - origin/master

which is kind of confusing? it seems all backwards. So how do I get out of this mess without losing all the work I did on the feature?

Visual Studio 2015 How to merge a branch into master?

I implemented the oauth2 web flow in order to get access_token from users of my app. With the access_token, I would like to do the following actions:  

1. Get user informations  
2. Create a repo for this user  
3. Push code to this repo (using git push &lt;remote&gt; &lt;branch&gt;)

I already successfully get the user information(1) and create a repo(2)

The problem is I can&#39;t push code (3), I got &quot;Unauthorized&quot; error.  


The command I run:


    git remote add origin https://gitlab-ci-token&lt;mytoken&gt;@gitlab.com/myuser/myrepo.git  
    git push origin master


gitlab - Push to a repository using access_token

I&#39;ve been doing my project while at some point I discovered that one thing stopped working. I needed to look up the state of my code when it was working correctly, so I&#39;ve decided to use git checkout (because I wanted to check-something-out). And so I&#39;ve done

    git checkout SHA

couple times while going back to point from which I can&#39;t go to HEAD, the output is following:

    git checkout SHA-HEAD
    
    error: Your local changes to the following files would be overwritten by checkout:
    	[list of files]
    Please, commit your changes or stash them before you can switch branches.
    Aborting

I am pretty much sure I have NOT changed anything. The command

    git checkout master

gives the same output.

Is there a way to go back to HEAD?

What is the safe way of &quot;jumping over&quot; history commits?


Git checkout - switching back to HEAD

How do I compare different branches in Visual Studio Code 1.9?

Is it possible?



How to compare different branches in Visual Studio Code

Inside a script I am trying to clone a GitHub repository with an OAuth token.

According to this tutorial:

https://github.com/blog/1270-easier-builds-and-deployments-using-git-over-https-and-oauth

I should be able to build a command for it like this:

    git clone https://&lt;token&gt;@github.com/owner/repo.git

If I try this manually with a proper access token, it still asks for my password.

If I try it on the commandline I am simply getting a `repository not found` error.

The article is from 2012 and I cannot find any API documentation for this. So I am wondering if this still works.

GitHub Clone with OAuth Access Token

# &quot;New&quot; Git Comment:

Just today I ran across the following comment from Git for the first time (at least the first time I saw it):

    Mikes-Mac$ git push
    Locking support detected on remote &quot;origin&quot;. Consider enabling it with:
      $ git config &#39;lfs.https://github.com/&lt;my_repo&gt;.git/info/lfs.locksverify&#39; true
    Everything up-to-date
    Mikes-Mac$ 

What is this `Locking support`? Is this some sort of [mutex locking](https://en.wikipedia.org/wiki/Mutual_exclusion) for the LFS (large file storage)? If so, isn&#39;t it absolutely essential to get anything on git to work?  (Minimally, how else could the &quot;ordering&quot; of the log history be established? Worse case, couldn&#39;t I have a binary file corrupted by simultaneous writes?)

# My Actions

I didn&#39;t do anything differently to this repository recently, nor have I done anything differently with this repository compared to any others that I&#39;ve established with LFS.

I&#39;m therefore assuming this is a new comment being provided to &quot;the world&quot; to let us know of new features.

# No Obvious Documentation

However, neither a Google search nor a *quick* search through their documentation led me to anything to explain this. So, I&#39;m left wondering:

 - What is this locking?
     - Is it mutex? If so, how could my repo even function without it?
     - Is this limited to just LFS? How is it different from normal git file locking?
 - What are the pros and cons of adding locking support for LFS?




Git (LFS): what is locking support? And should I enable it?

How to clean repo, if staged files marked as modified?

After 

    git reset --hard

I get 

    Encountered 7 file(s) that should have been pointers, but weren&#39;t:


Running `git clean -fdx` doesn&#39;t help, either.

Git error: Encountered 7 file(s) that should have been pointers, but weren&#39;t

I&#39;m trying to add everything under `MyProject/Frameworks/` to [git-lfs][1] (large file storage). I&#39;m [not sure][2] what the proper format for matching all files and folders recursively under the `Frameworks` folder is. [This answer][3] says the proper format is `git lfs track &quot;MyProject/Frameworks/**&quot;`, but [Atlassian&#39;s help document][4] says I should use `git lfs track &quot;MyProject/Frameworks/&quot;`. I tried both and they didn&#39;t use `git lfs` for storage. It tried uploading files directly.

Sure, I&#39;d love to know the proper format, but more importantly, before I attempt to push my changes to github, I&#39;d like to verify that the match and files do indeed work correctly. This&#39;ll allow me to iterate and try new things.

I see two related commands that might help: [`git lfs status`][5] and [`git lfs ls-files`][6]. It&#39;s not clear which one I should be using and what output I should be looking for. For example, when I ran `git lfs status`, it showed me a ton of files under `Git LFS objects to be committed`, making me think they would be added to Git LFS. However, after attempting to push to GitHub.com, I realized that it was clearly not the case. If it helps, the output for these files always had something like `(Git: edee1ad)` after each file name.

When I attempt to use `git lfs ls-files` I&#39;m not sure if I need to run it after `git add`ing the files, after committing them, or after pushing them. Most of the time it&#39;s just showing me blank output.

Essentially the question is: **If I configured `git lfs` correctly, what tool (e.g. `git lfs status`) should I use, and what output should I look for *before* I attempt to commit/push?**

**Note:** Please don&#39;t answer the question with _only_ how to match all recursive files as that will help me once (this specific case), rather than allowing me to iterate and try new things (any case).


  [1]: https://git-lfs.github.com
  [2]: https://stackoverflow.com/questions/35769330/git-lfs-track-folder-recursively#comment95711641_35769868
  [3]: https://stackoverflow.com/a/35769868/35690
  [4]: https://www.atlassian.com/git/tutorials/git-lfs#tracking-files
  [5]: https://github.com/git-lfs/git-lfs/blob/master/docs/man/git-lfs-status.1.ronn
  [6]: https://github.com/git-lfs/git-lfs/blob/master/docs/man/git-lfs-ls-files.1.ronn

Content Type	Original Author	Original Content on Stackoverflow
Question	ideasman42	View Question on Stackoverflow
Solution 1 - Git	Marcelo Ávila de Oliveira	View Answer on Stackoverflow
Solution 2 - Git	Alija	View Answer on Stackoverflow

How to clone/pull a git repository, ignoring LFS?

Git Problem Overview

Git Solutions

Solution 1 - Git

Solution 2 - Git

How to Log object?

Storing Objects in localStorage

Attributions