I have recently pushed to github, and see a white arrow on one of my folders.
and when i click on the folder, it does not open it. On my local machine, it has contents, but in github i cannot access them. What does this mean?
In both cases (white arrow with a folder name, or white arrow with folder @ xxx , folder name and version), it is a Gitlink represented a nested Git repository: a placeholder for another Git repository, hence an empty folder.
The arrow may mean that is a submodule. You could try: git add yourfolder. If that results in an error like: xxx submodule xxx. appears, you may try this: git rm --cached yourfolder. Then, you could successfully run: git add yourfolder.
1 Answer. You cannot create an empty folder and then add files to that folder, but instead, the creation of a folder must happen together with the addition of at least a single file. On Github you can do it this way: go to the folder within which you would like to make another folder.
Check if locally you have a .git/
sub-folder under that folder.
That would mean the folder (locally) is a nested Git repository, whose tree SHA1 is recorded as a "gitlink" (gray folder with straight white arrow)
What you would then see on GitHub is that gitlink: SHA-1 of the object refers to a commit in another repository, represented by an empty folder name. It is a nested Git repository.
If you see a folder @ xxx
, then it is a submodule entry, meaning your own repository has a .gitmodules
in it, which records, in addition of the gitlink, the actual URL of the remote repository.
It represents the object name of the commit that the super-project expects the nested submodule's working directory to be at.
In both cases (white arrow with a folder name, or white arrow with folder @ xxx
, folder name and version), it is a Gitlink represented a nested Git repository: a placeholder for another Git repository, hence an empty folder. But in the second case, that empty folder would be referenced/visible in a special .gitmodules
file.
In order to restore that folder content:
A git clone --recurse-submodules
would restore the content of that submodule in your local repository (as opposed to a nested Git repo, where its URL is not recorded, and the content of the folder would remain empty)
The white arrow would remain on the remote repository, with folder @ version
displaying what SHA1 of the submodule repository is referenced by your project.
Alternatively, you could, if you don't care about the history of that folder, delete locally its .git
subfolder (assuming it is not a submodule, meaning it is not referenced in a .gitmodules
file in your main repository), add, commit and push.
The white arrow would then disappear, and you would be able to access that folder content on GitHub.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With