CI that doesn't run on MRs

[Nate Graham]

On 8/20/25 13:07, Ben Cooksley wrote:
> On Thu, Aug 21, 2025 at 7:02 AM Nate Graham <nate at kde.org 
> Just having a look at KWin at least, looks like the majority of MRs 
> aren't draft.
> 
> Before I make that change, which is really just removing the force-to- 
> manual-for-Plasma, could folks please go through outstanding MRs and 
> mark those that aren't ready to merge as draft?


If we're going to do this, it will require some formal communication, 
documentation, and a transitional period.

It will also require some understanding that whether a merge request is 
"ready to merge" or not isn't black-and-white. When you submit your MR, 
you certainly think it's ready to merge. Then you get review comments 
and make changes. Who's to say the CI shouldn't run on the changes you 
just made, to make sure they didn't break anything?

I can see us marking merge requests as Draft if we *know* there's going 
to be heavy iteration over an extended period of time (for example 
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/5563), 
and that's what needs to be communicated broadly to align everyone's 
expectations.


Nate