Rename project and group-level runner permissions

What does this MR do and why?

We have runner-related permissions both at the runner level, and at the group/project level. They all share the same name (singular form), but in preparation for a follow-up MR where we merge admin_project_runners and admin_runner, I'm renaming the group/project-level permissions to the plural form:

MR old name new name
!196387 (merged) ⬅️ :admin_runner :admin_runners
!196387 (merged) ⬅️ :create_runner :create_runners
!196387 (merged) ⬅️ :create_instance_runner :create_instance_runners
!196387 (merged) ⬅️ :read_runner :read_runners
!196390 (merged) :admin_project_runners :admin_runners
!196390 (merged) :read_group_runners :read_runners
!196390 (merged) :read_project_runners :read_runners

References

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Pedro Pombeiro

Merge request reports

Loading