Convert to GitlabCI

The pipeline should run on merge request after committing the .gitlab-ci.yml file according to https://www.drupal.org/docs/develop/git/using-gitlab-to-contribute-to-dr... → .

However currently Gitlab shows this under the pipelines tab on the merge request:

Pressing the Run Pipeline button produces the error message "An error occurred while trying to run a new pipeline for this merge request."

I have not hit this issue with any other modules I've recently tried to convert to Gitlab.

Postponing as I think we need a maintainer to check the configuration for this project in Gitlab.

Looks like this is blocked on 🐛 GitLabCI does not allow MRs from forks opened by non-members to run in the parent project Fixed

Un-postponing now I have maintainership; pushing an empty commit to see if tests now run on gitlab.

Gitlab CI fails on composer step:

Your requirements could not be resolved to an installable set of packages.
  Problem 1
    - drupal/core-recommended 10.1.x-dev requires drupal/core 10.1.x-dev -> found drupal/core[10.1.x-dev] but it conflicts with your root composer.json require (^9.0).
    - drupal/core-recommended 10.1.0-alpha1 requires drupal/core 10.1.0-alpha1 -> found drupal/core[10.1.0-alpha1] but it conflicts with your root composer.json require (^9.0).
    - drupal/core-recommended 10.1.0-beta1 requires drupal/core 10.1.0-beta1 -> found drupal/core[10.1.0-beta1] but it conflicts with your root composer.json require (^9.0).
    - drupal/core-recommended 10.1.0-rc1 requires drupal/core 10.1.0-rc1 -> found drupal/core[10.1.0-rc1] but it conflicts with your root composer.json require (^9.0).
    - drupal/core-recommended 10.1.0 requires drupal/core 10.1.0 -> found drupal/core[10.1.0] but it conflicts with your root composer.json require (^9.0).
    - drupal/core-recommended 10.1.1 requires drupal/core 10.1.1 -> found drupal/core[10.1.1] but it conflicts with your root composer.json require (^9.0).
    - drupal/core-recommended 10.1.2 requires drupal/core 10.1.2 -> found drupal/core[10.1.2] but it conflicts with your root composer.json require (^9.0).
    - Root composer.json requires drupal/core-recommended 10.1.x -> satisfiable by drupal/core-recommended[10.1.0-alpha1, ..., 10.1.x-dev].

Whilst it would be good to conclude this issue with a clean sweep of ESLint fixes, the remaining issues require more thought and consideration and I'd like to prioritise the D10 port now we have working tests.

Looks like the JS changes made by PHPCBF in https://git.drupalcode.org/project/flysystem_s3/-/merge_requests/11/diff... break the filefield upload to S3.

Have disabled ESLint for now and raised 📌 Fix ESLint Issues Active to fix ESLint issues and restore it to the CI pipeline.

Drupal.org test schedules are now removed.

Automatically closed - issue fixed for 2 weeks with no activity.