Use persisted/memoized value for MRs sha's instead of doing git lookups
What does this MR do?
Use persisted/memoized value for MRs sha's instead of doing git lookups
Are there points in the code the reviewer needs to double check?
No
Why was this MR needed?
Commit lookup can be very costly, especially in a post-Gitaly world and considering that Merge Requests get queried a lot on AJAX requests
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added -
Tests added for this feature/bug - Review
-
Has been reviewed by UX -
Has been reviewed by Frontend -
Has been reviewed by Backend -
Has been reviewed by Database
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Squashed related commits together -
Internationalization required/considered -
End-to-end tests pass ( package-qamanual pipeline job)
What are the relevant issue numbers?
Helps with gitaly#1055 (closed)
Edited by Alejandro Rodríguez