Yes, this is an consequence of a bug in gitlab which meant that pushes to branches which were also MRs were built twice.
I'm not sure there is a way to manually trigger the CI pipeline. If you really want to you could modify the .gitlab-ci.yml file on your branch. If you want your commit to be built you could make a MR? Cheers, Matt On Mon, Apr 8, 2019 at 2:22 PM Sylvain Henry <[email protected]> wrote: > > Hi devs, > > It seems that the CI doesn't check branches in GHC forks on Gitlab > anymore. Is is intentional? Is there a way to trigger a CI execution > manually on a specific branch? > > Thanks, > Sylvain > > _______________________________________________ > ghc-devs mailing list > [email protected] > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs _______________________________________________ ghc-devs mailing list [email protected] http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
