Optimistic locking for Issue and Merge Requests (!5146) · Merge requests · GitLab.org / GitLab FOSS · GitLab

The 17.0 major release is coming on May 16, 2024! This version brings many exciting improvements to GitLab, but also removes some deprecated features. We are introducing three breaking change windows during which we expect breaking changes to be deployed to GitLab.com. You can read more about it on our blogpost . The third breaking change window begins 2024-05-06 09:00 UTC and ends 2024-05-08 22:00 UTC.

Valery Sizov requested to merge lock_for_issuable into master Jul 07, 2016

What does this MR do?

It implements Optimistic Locking http://api.rubyonrails.org/classes/ActiveRecord/Locking/Optimistic.html for Issues and MRs but in a bit custom way. We use it for cases when either title or description field is involved in the change.

Why was this MR needed?

We have to prevent data losing.

What are the relevant issue numbers?

https://gitlab.com/gitlab-org/gitlab-ce/issues/12940

Screenshots (if relevant)