Help
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Copilot Lvl 2
Message 1 of 2

Git Repo does not use latest commit for file (through GitLab)

Solved! Go to Solution.

Hi, not sure if this relates to GitLab or is a common Git issue. There are several files in our repository which were modified in the last weeks but are effectively displayed and delivered as old revisions. Here is one example:

 

File production.logback-spring.xml in master-Branch shows commit d26c60fb from 12 Nov 2018. Even when I pull the repo with master-Branch, this file gets delivered. But I committed a newer version on 14 Jan 2019. This is shown correctly as last committed file in File History in master-Branch.

 

I don’t understand what’s going on here. Is this a common Git behaviour I don’t know about?

 

Thanks

Jeong

 

File History:

Bildschirmfoto 2019-01-22 um 11.21.23.png

 

File View (content of old commit d26c60fb is showing and really gets delivered when pulling repo)

Bildschirmfoto 2019-01-22 um 11.24.22.png

 

1 Reply
Solution
Copilot Lvl 2
Message 2 of 2

Re: Git Repo does not use latest commit for file (through GitLab)

It is just a display error in GitLab. There was a merge into master which reverted my last commit, but this did not show up in GitLab.