We added caching to merge requests' list of commits previously (
allura.model.repository.MergeRequest#commits). But it still can sometimes be slow the very first time. This is particularly a problem when creating the merge request and there's been no chance for it to get cached.
There is a similar pattern in place already for seeing if the commits are cleanly mergeable (see "merge_task_status")
Log in to post a comment.