Make tags and run untagged jobs required for runner creation
Details
When filling out details about the new runner, you must check Run untagged jobs if you do not add tags to the runner. I want to make it more clear that tags OR Run untagged jobs is necessary in order to create the runner (we mark both as optional, so it's confusing right now).
Proposal
- Currently, we have two versions of basically the same form, one version to
createand anotherupdate. In order to have this improvement propagate to bothcreateandupdate, we'll first work on refactoring both forms to use the same implementation. - When creating a project runner, we may include the
lock to current projectswithin the form. This depends on permission control investigation findings. - The new (consistent) form should separate the tags options into a new section.
- Figma file
Edited by Gina Doyle
