Mark issues needs work when MRs can't be merged or pipelines fail

Created on 13 September 2023, 10 months ago

Updated 31 October 2023, 8 months ago

Problem/Motivation

DrupalCI currently incorporates RTBC retesting of patches and MRs, it would be useful to have similar functionality on GitLab CI.

📌 [PP-1] MR retesting with GitLab CI Postponed is open but gitlab already handles the 'update a stale branch' situation pretty well. What we're more likely to miss is automatically marking the issue needs work when the MR can't be merged or the pipeline fails.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

📌 Task

Status

Active

Version

3.0

Component

Code

Created by

🇬🇧United Kingdom catch

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @catch
Comment 10 months ago →
🇬🇧United Kingdom catch
Comment 8 months ago →
🇺🇸United States drumm NY, US
Some discussion is at #3178267: Update issue status on merge request activity? → as well

GitLab does make the pipeline status more scannable in the merge request listing, https://git.drupalcode.org/project/drupal/-/merge_requests, so you can see what is failing, with no additional tooling needed.

In the long run, will maintainers be looking at MRs first, or issues first? Some amount of issue review will always be needed for changes that do not land in code.

contrib.social Blog FAQ Discussions

Production build 0.69.0 2024