GitLab showing modified folders instead of files

Question

We are using git for source control using GitLab. The problem is, I created a new branch with no uncommitted files in the repository from where i created the branch and it is showing the modified folder and not files as follows,

# On branch 114531
# Changes not staged for commit:
#   (use "git add <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#   (commit or discard the untracked or modified content in submodules)
#
#   modified:   lib/library/CL (new commits)
#   modified:   lib/library/FW (new commits)
#   modified:   plugins/CPP (new commits, modified content)
#   modified:   plugins/CRBP (new commits)
#   modified:   plugins/CUP (new commits)
#   modified:   plugins/SLP (new commits)
#   modified:   plugins/SIP (new commits)
#
no changes added to commit (use "git add" and/or "git commit -a")

What is actually wrong? Why i'm not seeing files and only seeing folders? And how to make it to show all the modified files instead of folder? Please help friends.

How did you create the branch? – Nikhil Gupta Mar 10 '14 at 07:27 — Nikhil Gupta, Mar 10 '14 at 07:27
@NikhilGupta By using the command "git branch 114531" – Stranger Mar 10 '14 at 07:28 — Stranger, Mar 10 '14 at 07:28
and how did you checkout the new branch? – Nikhil Gupta Mar 10 '14 at 07:38 — Nikhil Gupta, Mar 10 '14 at 07:38
@NikhilGupta Using "git checkout 114531" – Stranger Mar 10 '14 at 08:06 — Stranger, Mar 10 '14 at 08:06

score 2 · Answer 1 · edited May 23 '17 at 12:23

why i'm not seeing files and only seeing folders?

Because those are submodule entries which reports new commits.

If you have done new commits in those submodule, you should push those, and go back to the parent repo (the one where you currently are), add those submodule entries (git add .), commit and push.

A git submodule update would reset those submodule to their original state.

See more at "Ignore new commits for git submodule".

score 0 · Answer 2 · answered Mar 10 '14 at 08:17

I believe all these folders were marked as modified before you created the branch and you chose not to reset those changes when you checked out the new branch (git checkout --force <branchname> would have removed the modified content from the new branch)

GitLab showing modified folders instead of files

2 Answers2