Use authorize_update_pipeline_schedule in PipelineSchedulesController
requested to merge dosuken123/gitlab-ce:33082-use-update_pipeline_schedule-for-edit-and-take_ownership-in-pipelineschedulescontroller into master
What does this MR do?
For consistency
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts with master(if it does - rebase it please) -
Squashed related commits together
What are the relevant issue numbers?
Closes #33082 (closed)
Edited by Shinya Maeda