Forking a repository should keep the custom CI config path
Summary
A forked repository does not keep the custom CI config path that you might have configured. This means that there's no pipelines running in the fork and that any merge request submitted from this fork will not show the results of the checks that you have defined.
Steps to reproduce
- Create a project "A" in a group "X" and setup some CI with a custom config path (I used "debian/kali-ci.yml")
- Fork project "A" in your personal namespace.
- Push some changes in a new branch
- See that there's no pipeline created for this branch.
- Create a merge request against X/A and see that the merge request doesn't show any CI result
Example Project
Try forking https://gitlab.com/kalilinux/packages/impacket-scripts
Note that I manually edited the CI config path in my fork and I had to push my branch a second time to get it to run the pipeline. Before that the pipelines page would show me the empty view directing me to the documentation. It would not show me the page where I can manually trigger a pipeline.
What is the current bug behavior?
The custom CI config path is lost after a fork.
What is the expected correct behavior?
The custom CI config path should be kept after a fork.
Related Support Tickets (internal)
Edited by DeAndre Harris