Refactor Gitlab::Checks::ChangeAccess class
What does this MR do?
This MR refactors the code inside Gitlab::Checks::ChangeAccess because it is quite big and any new additions suppose to tangle even more the class.
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
Tests added for this feature/bug -
Conforms to the code review guidelines -
Conforms to the merge request performance guidelines -
Conforms to the style guides -
Conforms to the database guides -
Link to e2e tests MR added if this MR has Requires e2e tests label. See the Test Planning Process. -
EE specific content should be in the top level /eefolder -
For a paid feature, have we considered GitLab.com plans, how it works for groups, and is there a design for promoting it to users who aren't on the correct plan?
Edited by Francisco Javier López (ex-Gitlab)