CODEWITHSUNDEEP
gitlabgitlab-cigitlab-ci-runner
EMC
EMC

Reputation: 47

Forked repository still triggering pipeline even though all pipelines are removed - possibly from original repository?

I'm working with a forked repository, and currently unable to merge any changes due to a pipeline failure error message.

The original repository has a merge request pipeline to AWS, and I tried to set up a similar pipeline from the fork, but the pipeline kept failing. I have now deleted the runner, removed the gitlab-ci.yml from all branches including main, and disabled CI/CD in settings (all in the forked repository).

When I try to merge, I'm still receiving a pipeline failure error. The only time I have ever successfully merged a branch in the forked repository was when I merged it to main in the original repository. I have never been able to successfully merge into main in the forked repository.

I know almost nothing about CI/CD btw; the first time I even attempted to work with any of this was last week.

Apologies if this is light on detail - I don't even know what I need to share. All help very much appreciated.

Upvotes: 0

Views: 17

Answers (1)

EMC
EMC

Reputation: 47

For future reference - there was a setting in the forked repo that said something to the tune of pipelines must be successful - despite the absence of any pipeline code.

I disabled this and merges were no longer blocked.

Upvotes: 0

Related Questions