GitHub Community
Git Repo does not use latest commit for file (through GitLab) #22341
-
|
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: File View (content of old commit d26c60fb is showing and really gets delivered when pulling repo) |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
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. |
Beta Was this translation helpful? Give feedback.
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.