Best Practice for using include in .gitlab-ci.yml
Description of the problem
My CI configuration files are all now pointing to a file in the
master branch of a public repository.
If the contents of that file are unintentionally mangled, subsequent runs of any other project, dependent on that file, will fail.
I've essentially introduced brittleness into my workflow, and violated one of the core tenants of CI... revision everything so that your builds are reproducible.
What is GitLab's recommendation for ensuring I am depending on a fixed, revisioned, common configuration, while also ensuring that updating to the latest revision is easy?