Fix usability problem for file template

Problem to solve

The templates picker UI is confusing and has usability problems due to double terminology used for example .GitLab-ci.yml templates.

Intended users

Devon (DevOps Engineer)

Further details

This problem has been surfaced through the baseline experience recommendations effort of 2019 Q2: gitlab-design#518 (closed)

User thoughts:

There is a template option with the same name which I can apply. It is not clear if it has been applied already yes or no. Though the file seems empty.

Apparently this is for choosing different template types... Are those immediately related to setting up gitlab-ci?

Proposal

• Move closer to the template picker UI from issue descriptions and consolidate towards one button for template picking.
• It should be positioned next to the file name input like so: .
• This will make the template picker UI always available regardless of the file name.
• The dropdown search will be prefilled with the file name, so the search immediately filters the dropdown results to what is most interesting.
• The default dropdown results will now be named for example .GitLab-ci.yml - Docker
• Template applied functionality should be retained but can be made a default tertiary button instead of an info button similar to the Web IDE.

Permissions and Security

Documentation

Testing

What does success look like, and how can we measure that?

Links / references