[GitLab CI/CD for external repositories](https://docs.gitlab.com/ee/ci/ci_cd_for_external_repos/) feature is owned by ~"group::pipeline execution" however it's functionality is partially based on and dependent on GitHub importer code. As ~"group::import and integrate" works on the GitHub importer, it might happen that changes to the importer affect also GitLab CI/CD for external repositories functionality. Additionally, it is harder to assign issues to the correct group. Current example: - https://gitlab.com/gitlab-org/gitlab/-/issues/419532+ This issue is to assess the problem and possible solutions that would enable: * To have a clear ownership of the issues related to running GitLab CI/CD for external repositories functionality * To avoid cases when we make change to importer code and unwillingly affect running GitLab CI/CD for external repositories functionality as well. Possible solution could be to define and document the API that "running GitLab CI/CD for external repositories" expects, and cover it with tests.