ef00a864d1
A user reported internally: > It used to be the case that the submit button was greyed out if your > repo required fast-forward and your CL was out of date. Now there's > no obvious way to tell if a submit is likely to succeed without trying > it, which is a minor but daily annoyance. This may have been introduced with the `submitWholeTopic` feature recently. Looking at the code I suspect that there was a client side check for enabling the submit button as well as there is a client side class com.google.gerrit.client.changes.ChangeInfo.MergeableInfo. Part of the `submitWholeTopic` feature was moving responsibility more to the server and dumb down the client a bit. So now we also have to do this computation at the server side. Change-Id: I5dcd8c954446462660d45ead13eb38b6d8fa822a Signed-off-by: Stefan Beller <sbeller@google.com>