Improve user experience when disabling/re-enabling shared runners at the Group level
Proposal
Presently, when a user disables shared runners for a group, the projects in that group also have the shared runners disabled. However, when shared runners are re-enabled for the group, they are not also automatically re-enabled for all projects in the group. This requires an administrator to manually enable the shared runners again for projects via the UI, API, or Rails console.
Instead, I believe that we can improve this flow for users via the following:
- Add a warning to the toggle that indicates that all projects in the group will also have the shared runners disabled
- Retain the state of the shared Runners toggle at the project level when disabled at the group level, and return the projects to that state if later re-enabled at the group level
- When re-enabling the shared runners for a group, present users with the option to enable shared runners for all member projects
By exploring these options, we can make the flow for disabling and re-enabling shared runners within a group clearer to users, to help them understand the result of the action.