Remove unneeded can_pull and can_push checks for ee mirror_repos_form
requested to merge 7433-mirroring-repos-direction-select-empty-and-consistency-across-offerings into master
What does this MR do?
the ee mirror_repos_form has several checks for can_push and can_pull. These are not needed as the user can do both if they can view that partial.
-
remove cases of can_pull -
remove cases of can_push
What are the relevant issue numbers?
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?
Closes #7433 (closed)
Edited by Luke Bennett