The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

destop.ini has null OID

Rushikesh Ganachari
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 17, 2024

git -c filter.lfs.smudge= -c filter.lfs.required=false -c diff.mnemonicprefix=false -c core.quotepath=false --no-optional-locks clone --branch master //GITSERVER/Releases/BICS/BenchMark/BenchMark.git "C:\Rushikesh\New folder"
Cloning into 'C:\Rushikesh\New folder'...
done.
fatal: 'refs/remotes/origin/desktop.ini' has a null OID
Completed with errors, see above.

 

Getting this while Cloning the Code

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Martin Runge
Community Champion
April 29, 2026

Hi @Rushikesh Ganachari

Welcome to the Atlassian community!

This error usually happens when Git finds a tracked file, like desktop.ini, missing its data object in the Git database, often due to a corrupted push or shallow clone.
You can try these steps to resolve it:

  1. Check the remote repository to see if a file was added accidentally. Remove it from the repository's tracking, commit, and push.
  2. Force a fresh clone without LFS filters: 
    git clone -c filter.lfs.smudge=false -c filter.lfs.required=false <repo_url>

Once resolved, add desktop.ini or else to your .gitignore file to prevent Windows system files from being tracked in the future.

TAGS
AUG Leaders

Atlassian Community Events