GitXplorerGitXplorer
r

test-submodules-with-symlinks

public
2 stars
1 forks
0 issues

Commits

List of commits on branch master.
Verified
befd41644307dab94637b042dbfe7f3152e712b0

Update Readme.md

rrafeca committed 4 years ago
Verified
de17a1b8f848c59be73bb9fb23b72e45250c0359

Update Readme.md

rrafeca committed 4 years ago
Verified
c70e0a0a2a8430d9bcece7f1e7ad18be335b20da

Update Readme.md

rrafeca committed 4 years ago
Verified
b4b013a2caae6169c6e226ead66fb874b3fed077

Add Readme.md

rrafeca committed 4 years ago
Verified
55f10bdbf28d40b18ce75137ade0e7171ba39515

Add gitignore submodule

rrafeca committed 4 years ago
Verified
d1f297e2ece301033c6fa85d96d21b4d9166201a

Fix workflow file

rrafeca committed 4 years ago

README

The README file for this repository.

Git for Windows issue with core.symlinks=true

This repository acts as an easy way to reproduce a current issue in git for windows (v2.27.0) which is related to the core.symlinks setting.

Steps to reproduce the problem:

Clone the repository locally with core.symlinks=true:

$ git -c core.symlinks=true clone https://github.com/rafeca/test-submodules-with-symlinks.git
$ cd test-submodules-with-symlinks
$ git -c core.symlinks=true submodule update --init --force --recursive

After cloning, there are unexpected local changes in your working directory:

$ git diff
diff --git a/gitignore b/gitignore
--- a/gitignore
+++ b/gitignore
@@ -1 +1 @@
-Subproject commit 218a941be92679ce67d0484547e3e142b2f5f6f0
+Subproject commit 218a941be92679ce67d0484547e3e142b2f5f6f0-dirty

Checking the status on the gitignore folder shows symlinks as modified files:

$ cd gitignore && git status
HEAD detached at 218a941
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
        modified:   Clojure.gitignore
        modified:   Fortran.gitignore
        modified:   Global/Octave.gitignore
        modified:   Kotlin.gitignore

no changes added to commit (use "git add" and/or "git commit -a")

Expected behaviour

After cloning the repository, both git diff and git status should show no changes.