Add "Go Back To Runners" link after saving changes to a runner

Description

(Include problem, use cases, benefits, and/or goals)

If you edit the settings for a runner (Settings --> CI/CD Pipelines --> Edit icon by a runner) and save the changes you are taken to a page that has information about the runner, but no way to get back to the CI/CD Pipelines without going through Settings again.

Proposal

It would be beneficial to have a link on this runner information page to "Go Back To CI/CD Pipelines" or "Go Back To Runners" to continue the administrative flow of editing further runners.

Links / references

#24141 (moved) appears to be an overhaul of the way the project runner settings will be displayed in the near future. However, this issue can either be viewed as a small subset of that, or a stop-gap measure until it is completed.

Documentation blurb

https://docs.gitlab.com/ce/ci/runners/README.html

This already existing documentation page could add a section on "Editing Existing Project Runners". The actual wording of the section might be best if added in #24141 (moved) since that appears to be more comprehensive, but it might be as simple as:

Once your project has at least one runner registered, you can edit the settings of any runner by clicking the edit icon next to any runner. This will take you to a page where you can edit the following

• Active
• Run untagged jobs
• Lock to current project
• description
• tags

Proposed labels: frontend, CI, feature proposal

@flamableconcrete Thanks for the feedback. I believe this is the project specific runner's show page that you are referring to, that is visible after committing changes to the specific runner via the form?

• https://gitlab.com/gitlab-org/gitlab-ce/blob/master/app/views/projects/runners/show.html.haml

Please can you confirm?

/cc @dimitrieh

added ~19173 ~19492 feature proposal settings labels

Yes, this is referring to the project specific runner show page. And thanks for adding the labels!

This appears to be a duplicate of the following issue that has been opened for a Community Contribution:

• https://gitlab.com/gitlab-org/gitlab-ce/issues/17289

Closing this down in favour of the original proposal

closed