Allow include:file:ref patterns (mainly for semver)

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Problem to solve

As a developper, I'd like to be able to have a kind of semver for the files I include in my CI.

This would allow me to :

• Update the included files safely.
• Allow my project to use the new CI changes without any changes (ex: changing the include:file:ref ).

Intended users

Developer

User experience goal

The user should be able to update a CI included file without fear of breaking projects

Proposal

The most straightforward solution would be to allow patterns in the CI include:file:ref

For example you could have :

include:
  - project: 'my-group/my-project'
    ref: v1.x.x
    file: '/templates/.gitlab-ci-template.yml'

Further details

Permissions and Security

Documentation

Availability & Testing

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

What is the type of buyer?

Is this a cross-stage feature?

Links / references