Ensure consistent naming of Gitlab in class names
What does this merge request do and why?
Ensure consistent naming of Gitlab in class names.
Gitlab
seems to be a more popular choice than GitLab
when naming classes in the GitLab Rails monolith
❯ rg "Gitlab[A-Za-z_]" --type go --type ruby -l | wc -l
1905
❯ rg "GitLab[A-Za-z_]" --type go --type ruby -l | wc -l
28
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Merge request checklist
-
I've ran the affected pipeline(s) to validate that nothing is broken. -
Tests added for new functionality. If not, please raise an issue to follow up. -
Documentation added/updated, if needed.
Edited by Tan Le