Follow-up from "Add variables to pipelines schedules"
The following discussion from !12372 (merged) should be addressed:
-
@ayufan started a discussion: (+3 comments) Does it mean if condition
protected_action
is true we preventupdate_schedule
?I think that this reads wrong, as this is not very descriptive.
I wonder if we should not change the naming of that:
condition(:allowed_to_edit) do pipeline_schedule.project.team.master?(@user) || pipeline_schedule.owned_by(@user) end rule { !allowed_to_edit }.prevent :update_piepline_schedule