gitlab-org--gitlab-foss/app
Stan Hu dbc03ce3a9 Optimize merge request refresh by using the database to check commit SHAs
Previously for a given merge request, we would:

1. Create the array of commit SHAs involved in the push (A)
2. Request all merge request commits and map the SHA (B)
3. Reload the diff if there were any common commits between A and B

We can avoid additional database querying and overhead by
checking with the database whether the merge request contains any
of the commit SHAs.

Relates to https://gitlab.com/gitlab-org/gitlab-ce/issues/53213
2018-11-02 12:11:30 -07:00
..
assets Merge branch '51620-cannot-add-label-to-issue-from-board' into 'master' 2018-11-02 13:24:22 +00:00
controllers Merge branch 'top_level_clusters_controller' into 'master' 2018-11-02 12:34:40 +00:00
finders Merge branch 'top_level_clusters_controller' into 'master' 2018-11-02 12:34:40 +00:00
graphql
helpers Merge branch 'top_level_clusters_controller' into 'master' 2018-11-02 12:34:40 +00:00
mailers Add email for milestone change 2018-11-02 16:29:32 +00:00
models Optimize merge request refresh by using the database to check commit SHAs 2018-11-02 12:11:30 -07:00
policies
presenters Merge branch 'top_level_clusters_controller' into 'master' 2018-11-02 12:34:40 +00:00
serializers Add scheduled flag to job entity 2018-11-02 11:52:34 +00:00
services Optimize merge request refresh by using the database to check commit SHAs 2018-11-02 12:11:30 -07:00
uploaders
validators
views Add email for milestone change 2018-11-02 16:29:32 +00:00
workers Incorporates Kubernetes Namespace into Cluster's flow 2018-11-02 15:46:15 +00:00