Follow-up from "Add "SHA mismatch" state to the MR widget"
The following discussion from !11316 (merged) should be addressed:
-
@DouweM started a discussion: (+3 comments) @mikegreiling If I'm not mistaken, this will still send the latest SHA along with the form, which overrides the server side validation if for whatever magic reason someone manages to submit the form anyway. I think the SHA we send in the form should always be the original SHA, and we can of course use the new SHA to conditionally show this error.