We have a central repository holding all of our CI configuration. Each project we have includes the neccessary files from that central repository. The conditions for running the jobs are present in the external files and make sure the pipeline only runs for specific branches.
Now we have a situation where a few developers are working on a project, but don't have access to the central repository. Whenever they commit Gitlab tries to setup a pipeline but fails because the developers don't have access.
Is there a way to add some logic to the gitlab-ci.yml that executes before including the files from the central repository? And as such effectively stop the pipeline from being created and include the external files.