Docs - product feedback: Creating a new file may erroneously include commit history from different files in the repo
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
When one creates a new file in a repo, it's quite expected that there will be no prior commit history attached to the file. However, I have been noticing a weird bug where creating a new file may erroneously include the commits from different files completely unrelated to the newly created file.
For example, to recreate the issue, create a new file in a repo with any name and no content(i.e empty file). Then, again create a new file in a repo with any name(but different from the first file we created) and no content(i.e empty file).
If you view the commit history of the second file, you will notice that the commit from the creation of the first file is included in the history. (One way to view the commit history for a file via the GitLab website is to click on the file in a repo -> click the "History" button)
I have noticed the same issue occurs not only for files that were both created with empty content but also for files that were originally created with identical contents.