Skip to content

Set the urgency to low for status checks API

What does this MR do and why?

Set low urgency for projects/:id/merge_requests/:merge_request_iid/status_checks API. This API is usually used by automations and therefore setting the urgency to low is acceptable. The avg. time for this API is 1.47s and majority of the time is spent by CPU as seen by cpu_s column.

image

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #421379 (closed)

Merge request reports