Skip to content

Resolve "`merge_status` is inconsistent across different users and does not refresh on API request"

What does this MR do and why?

merge_status is inconsistent across different users and does not refresh on API request.

There are two issues here, one is that the cache doesn't get updated when the merge_status of the merge request changes, so the old merge_status is returned. This is fixed by adding the merge_status to the cache key, and the second issue is that when we do cache the object, it means that the recheck mergeability parameter is ignored.

Testing instructions:

#365299 (comment 997085415)

Related to #365299 (closed)

Edited by Marc Shaw

Merge request reports

Loading