On Mon, Aug 11, 2025 at 2:31 AM Nate Graham <n...@kde.org> wrote: > On 8/10/25 8:06 AM, Nate Graham wrote: > > On 8/7/25 1:06 PM, Ben Cooksley wrote: > >> On Fri, Aug 8, 2025 at 2:55 AM Nate Graham <n...@kde.org > >> <mailto:n...@kde.org>> wrote: > > > >> Is this working? I'm not seeing it happen. When a Plasma-aligned > >> merge > >> request is approved and then rebased, pipelines still aren't > starting > >> automatically. > >> > >> > >> Links to affected MRs would be helpful please :) > > > > Here's an example: https://invent.kde.org/plasma/plasma-workspace/-/ > > merge_requests/5743 > > And another: > https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/3149 > > None of them seem to be running all pipelines automatically after > rebasing following an approval. >
Unfortunately the variable in question we were trying to rely on, CI_MERGE_REQUEST_APPROVED is exclusive to Enterprise Edition: ben@sapphire:~/workspace/gitlab> grep -ir CI_MERGE_REQUEST_APPROVED * ee/app/models/ee/merge_request.rb: variables.append(key: 'CI_MERGE_REQUEST_APPROVED', value: approved?.to_s) if approved? As such that functionality is not available to us. This means the options available to us are: - Using a custom label (accessible via CI_MERGE_REQUEST_LABELS) - Making use of the functionality to mark merge requests as draft until they're actually ready for merging (accessible via CI_MERGE_REQUEST_DRAFT) > Nate > Thanks, Ben
