Deleting GL15.jpg as it duplicates gl15.jpg
Why is this change being made?
When I did a fresh git clone
of www-gitlab-com
I received the following error:
warning: the following paths have collided (e.g. case-sensitive paths
on a case-insensitive filesystem) and only one from the same
colliding group is in the working tree:
'source/images/blogimages/GL15.jpg'
'source/images/blogimages/gl15.jpg'
It appears !105818 (merged) was merged on 2022-06-13 which added gl15.jpg and !105551 (merged) was merged on 2022-06-20 which added GL15.jpg.
I downloaded and verified the files are identical:
% sha256sum gl15.jpg
d47f8df18d59176c31dd803f8e7d75fe6ee8df7c5e39c0a3abaaaa50d6d969b5 gl15.jpg
% sha256sum GL15\ \(1\).jpg
d47f8df18d59176c31dd803f8e7d75fe6ee8df7c5e39c0a3abaaaa50d6d969b5 GL15 (1).jpg
Given these files are identical, I've deleted GL15.jpg
and updated references to GL15.jpg
to point to gl15.jpg
to prevent this warning from occurring. I chose gl15.jpg
as it was merged first.
Author Checklist
-
Provided a concise title for this Merge Request (MR) -
Added a description to this MR explaining the reasons for the proposed change, per say why, not just what - Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
-
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
Maintained by
section on the page being edited - If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR - If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.