Rename all templates to *.gitlab-ci.yml

To make use of the autocompletion and linting available via the official GitLab extension for VSCode (I'm sure similar things exist for other IDEs) we should rename all of the templates in this project to follow the *.gitlab-ci.yml naming convention as this is how these extensions and linters etc. will determine that a specific yaml file is in fact a gitlab-ci type file.

Obviously, this is a breaking change. So, we would need to bump the repo to a new v3.0.0 release.

Here is an example of the vscode autocomplete suggesting the predefined CI variables in a drop-down list #winning!

added teamCloud workflowNeeds Refinement labels

changed the description

mentioned in merge request !58 (closed)

Since this is VSCode specific, would it not be far simpler to, rather than force a breaking change, create a .vscode/settings.json file in the root of the repo with

"files.associations": {
    "**/*.yaml": "gitlab-ci"
}

in it? (Replacing "gitlab-ci" with whatever the language mode identifier shown in the Change Language Mode (⌘K M) dropdown is.)

Alternatively, and I'm not familiar enough with VSCode to know the answer to this, does VSCode support something like vim modelines? E.g. for vim I could add a comment to a file like the following to force a particular syntax highlighting mode if I couldn't configure my editor any other way:

# vim:filetype=gitlab-ci

Looking at the source code for the extension, this may not work since this is a completion provider rather than a language mode.

Nonetheless, I don't really think it is appropriate to force a breaking change on all users of this repo for the sake of one editor and to avoid having https://docs.gitlab.com/ee/ci/variables/predefined_variables.html open in another tab.

I'd much rather open a MR on the VSCode extension itself to a) register the GitLab CI YAML as a language extension and b) pass the language id to registerCompletionItemProvider. This is, according to the scant docs I can find, more the "expected" form of a document selector, not a file glob.

Interestingly, I'm not alone in this opinion: https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/issues/819. (Edit: the opinion being that "language id"s should be used where possible, that is.)

Discussion at refinement:

• We shouldn't update the YAML file names
• We should add documentation to add the file association details.

added workflowSprint Ready label and removed workflowNeeds Refinement label

changed iteration to Cloud Team Sprints Aug 16, 2023 - Aug 29, 2023

removed iteration Cloud Team Sprints Aug 16, 2023 - Aug 29, 2023

changed iteration to Cloud Team Sprints Aug 30, 2023 - Sep 12, 2023

removed iteration Cloud Team Sprints Aug 30, 2023 - Sep 12, 2023

changed iteration to Cloud Team Sprints Sep 13, 2023 - Sep 26, 2023

assigned to @rk725

added workflowIn Progress label and removed workflowSprint Ready label

mentioned in merge request !63 (merged)

Moving this to workflowReview Required. This ended up being super easy to fix with a VSCode workspace setting to tell all yaml files to use the GitLab schema.

added quick to review workflowReview Required labels and removed workflowIn Progress label

mentioned in commit c9f8ae1f

closed with merge request !63 (merged)

added workflowDone label and removed workflowReview Required label

mentioned in merge request !83 (merged)