Problem/Motivation

There’s no way to trigger a test against an MR if the project doesn’t have issue testing set by default. See for example:

In the second example it wasn't possible to test against the correct version with the patch either.

See also https://drupal.slack.com/archives/C51GNJG91/p1634732599270600

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Comments

AndyF created an issue. See original summary.

drumm’s picture

Project: Drupal.org customizations » Project issue file test

https://git.drupalcode.org/project/project_issue_file_test/-/blob/0dde72... looks like the first thing to sort out. The previous tests are used to determine the merge target & release. I expect this can be determined another way.

drumm’s picture

Status: Active » Closed (outdated)