- First commit to issue fork.
- last update
about 1 year ago 5 pass - Status changed to RTBC
about 1 year ago 1:33pm 14 October 2023 - 🇳🇱Netherlands eelkeblok Netherlands 🇳🇱
It's a bit confusing, Drupal.org told me that the MR was ready to merge, but GitLab said there was a problem. It may have had to do with Drupal.org reporting the target to be 8.x-1.x while GitLab has 2.0.x as its target (btw, I would suggest to use 2.1 as the release version once this is merged, since this is a new feature). Either way, I merged 2.0.x into the MR branch, which seems to have satisfied GitLab. Maintainer should have the option to merge right from the issue, which will squash the whole thing down into a single commit on the current 2.0.x branch (again. consider making a 2.1.x branch and changing the MR target before doing so).
Would love to see this in the module, would make it even more useful.