Do not run CI on draft merge requests #6850

New Issue

GiteaMirror · 2025-11-02T07:08:35-06:00

GiteaMirror commented

2025-11-02 07:08:35 -06:00

Originally created by @Kreyren on GitHub (Feb 12, 2021).

Recommending to configure DroneCI to not run on draft merge requests.

Rationale

Draft merge requests doesn't need CI so this way we can preserve processing resources.

Originally created by @Kreyren on GitHub (Feb 12, 2021). Recommending to configure DroneCI to not run on draft merge requests. ### Rationale Draft merge requests doesn't need CI so this way we can preserve processing resources.

GiteaMirror added the type/proposal type/question labels 2025-11-02 07:08:35 -06:00

GiteaMirror closed this issue

2025-11-02 07:08:35 -06:00

GiteaMirror commented

2025-11-02 07:08:36 -06:00

@a1012112796 commented on GitHub (Feb 12, 2021):

suggested solutions:

add [SKIP CI]on commit message
add some logic on CI file to skip.

@a1012112796 commented on GitHub (Feb 12, 2021): suggested solutions: - add ``[SKIP CI]``on commit message - add some logic on CI file to skip.

GiteaMirror commented

2025-11-02 07:08:36 -06:00

@techknowlogick commented on GitHub (Feb 12, 2021):

We thankfully have generous sponsors who provide us with resources for our CI, and so running extra builds are fine. If the backlog of builds gets too backed up, we can manually cancel some as needed.

I also sometimes use draft PRs so I don't blast everyone with emails and still utilize our CI, so suggestion that @a1012112796 would be best if you don't want specific commits to build. However, a manager needs to be careful when merging your PRs as those skips would be added into the squash'd commit message and would skip the merge commit.

@techknowlogick commented on GitHub (Feb 12, 2021): We thankfully have generous sponsors who provide us with resources for our CI, and so running extra builds are fine. If the backlog of builds gets too backed up, we can manually cancel some as needed. I also sometimes use draft PRs so I don't blast everyone with emails and still utilize our CI, so suggestion that @a1012112796 would be best if you don't want specific commits to build. However, a manager needs to be careful when merging your PRs as those skips would be added into the squash'd commit message and would skip the merge commit.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#6850