Auto DevOps pipelines should run in forks
Problem to solve
If a fork of a project does not have Auto DevOps enabled and then the fork submits an MR then no pipeline will be available in that MR.
This is not ideal but it's not clear what the perfect solution here would be either. For example we can't make the Kubernetes cluster available for deployments in the fork since this would allow anyone that can fork to hijack our Kubernetes credentials for abuse. Without Kubernetes credentials we wouldn't be able to deploy a review app or do performance or DAST testing.
Intended users
Further details
This happened at gitlab-org/gitlab-services/design.gitlab.com!1492 (merged)
Workaround
For now you can workaround such a problem by pulling the forks branch locally and push it up as a new branch to the main repo from which it was forked. This will trigger a pipeline and then you can link to that pipeline from the MR to track it. This is manual but it at least tells us if it will pass and will also give a review app.
NOTE You should always look at someones MR before you push it to your own repo as they can easily include malicious code that steals our CI credentials. Never push someones branch to our main repo before you look at their code.