An error occurred fetching the project authors.
  1. 28 Aug, 2019 1 commit
  2. 21 Aug, 2019 1 commit
    • George Koltsov's avatar
      Add SortingPreference concern · 8bcc47ac
      George Koltsov authored
      Sorting preference functionality has been extracted
      from `IssuableCollections` to a new `SortingPreference`
      concern in order to reuse this functionality in projects
      (and groups in the future).
      8bcc47ac
  3. 05 Jul, 2019 1 commit
  4. 04 Jul, 2019 1 commit
    • Nick Thomas's avatar
      Allow asynchronous rebase operations to be monitored · 381468d0
      Nick Thomas authored
      This MR introduces tracking of the `rebase_jid` for merge requests. As
      with `merge_ongoing?`, `rebase_in_progress?` will now return true if a
      rebase is proceeding in sidekiq.
      
      After one release, we should remove the Gitaly-based lookup of rebases.
      It is much better to track this kind of thing via the database.
      381468d0
  5. 28 Jun, 2019 1 commit
  6. 22 Jun, 2019 1 commit
    • Stan Hu's avatar
      Enable Gitaly ref name caching for discussions.json · 30167193
      Stan Hu authored
      This eliminates many potential duplicate FindCommit RPCs for the same
      ref, which often occurs in the RelativeLinkFilter#current_commit call.
      On the GitLab 12.0 release post, for example, this would save close to
      400 RPC calls.
      30167193
  7. 20 Jun, 2019 1 commit
    • Oswaldo Ferreira's avatar
      Automatically update MR merge-ref along merge status · 3af348b6
      Oswaldo Ferreira authored
      This couples the code that transitions the `MergeRequest#merge_status`
      and refs/merge-requests/:iid/merge ref update.
      
      In general, instead of directly telling `MergeToRefService` to update
      the merge ref, we should rely on `MergeabilityCheckService` to keep
      both the merge status and merge ref synced. Now, if the merge_status is
      `can_be_merged` it means the merge-ref is also updated to the latest.
      
      We've also updated the logic to be more systematic and less user-based.
      3af348b6
  8. 12 Jun, 2019 1 commit
  9. 11 Jun, 2019 1 commit
  10. 03 Jun, 2019 1 commit
    • Shinya Maeda's avatar
      Abstract auto merge processes · d4b46936
      Shinya Maeda authored
      We have one auto merge strategy today - Merge When Pipeline
      Succeeds.
      
      In order to add more strategies for Merge Train feature,
      we abstract the architecture to be more extensible.
      
      Removed arguments
      
      Fix spec
      d4b46936
  11. 31 May, 2019 1 commit
    • Oswaldo Ferreira's avatar
      Automatically update MR merge-ref along merge status · b965009d
      Oswaldo Ferreira authored
      This couples the code that transitions the `MergeRequest#merge_status`
      and refs/merge-requests/:iid/merge ref update.
      
      In general, instead of directly telling `MergeToRefService` to update
      the merge ref, we should rely on `MergeabilityCheckService` to keep
      both the merge status and merge ref synced. Now, if the merge_status is
      `can_be_merged` it means the merge-ref is also updated to the latest.
      
      We've also updated the logic to be more systematic and less user-based.
      b965009d
  12. 16 Apr, 2019 1 commit
  13. 04 Apr, 2019 1 commit
    • Stan Hu's avatar
      Fix and expand Gitaly FindCommit caching · f2fa7c32
      Stan Hu authored
      https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/26248 added
      support for deduplicating FindCommit requests using Gitaly ref name
      caching. However, not all endpoints were covered, and in one case the
      Gitaly wrapper wasn't actually surrounding the serialization step. We
      can safely cache ref names between FindCommit calls for #index and #show
      endpoints for merge requests and pipelines. This can significantly
      reduce the number of FindCommit requests.
      f2fa7c32
  14. 27 Mar, 2019 1 commit
    • Stan Hu's avatar
      Allow ref name caching CommitService#find_commit · db759c5d
      Stan Hu authored
      For a given merge request, it's quite common to see duplicate FindCommit
      Gitaly requests because the Gitaly CommitService caches the request by
      the commit SHA, not by the ref name. However, most of the duplicate
      requests use the ref name, so the cache is never actually used in
      practice. This leads to unnecessary requests that slow performance.
      
      This commit allows certain callers to bypass the ref name to
      OID conversion in the cache. We don't do this by default because it's
      possible the tip of the branch changes during the commit, which
      would cause the caller to get stale data.
      
      This commit also forces the Ci::Pipeline to use the full ref name
      so that caching can work for merge requests.
      
      Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/57083
      db759c5d
  15. 26 Mar, 2019 1 commit
  16. 18 Mar, 2019 1 commit
  17. 06 Mar, 2019 1 commit
  18. 08 Feb, 2019 1 commit
  19. 06 Feb, 2019 1 commit
  20. 05 Feb, 2019 1 commit
  21. 28 Jan, 2019 1 commit
    • Mario de la Ossa's avatar
      Save sorting preference for Issues/MRs in BE · 49c74068
      Mario de la Ossa authored
      In order to let users' sorting preferences transfer between devices, we
      save the preference for issues and MRs (one preference for issues, one
      for MRs) in the backend inside the UserPreference object
      49c74068
  22. 24 Jan, 2019 1 commit
  23. 21 Dec, 2018 1 commit
    • Oswaldo Ferreira's avatar
      Cache diff highlight in discussions · 7cf49477
      Oswaldo Ferreira authored
      This commit handles note diffs caching, which considerably improves
      the performance on merge requests with lots of comments.
      Important to note that the caching approach taken here is different
      from `Gitlab::Diff::HighlightCache`. We do not reset the whole cache
      when a new push is sent or anything else. That's because discussions
      diffs are persisted and do not change.
      7cf49477
  24. 19 Dec, 2018 1 commit
  25. 07 Dec, 2018 1 commit
  26. 06 Dec, 2018 2 commits
  27. 23 Nov, 2018 1 commit
  28. 12 Nov, 2018 1 commit
  29. 31 Oct, 2018 1 commit
  30. 29 Oct, 2018 1 commit
  31. 26 Oct, 2018 1 commit
  32. 22 Oct, 2018 1 commit
  33. 18 Oct, 2018 1 commit
    • Alessio Caiazza's avatar
      Move ci_environments_status to a model · 4a9efc60
      Alessio Caiazza authored
      GET :namespace/merge_requests/:id/ci_environments_status complexity
      already reached a limit for a direct serialization from an hash
      computed at within the controller function.
      
      Here we introduce a virtual model EnvironmentStatus and its serializer.
      4a9efc60
  34. 05 Oct, 2018 1 commit
  35. 04 Oct, 2018 1 commit
  36. 26 Sep, 2018 1 commit
    • gfyoung's avatar
      Enable even more frozen string in app/controllers · 12ee2753
      gfyoung authored
      Enables frozen string for some vestigial files as
      well as the following:
      
      * app/controllers/projects/**/*.rb
      * app/controllers/sherlock/**/*.rb
      * app/controllers/snippets/**/*.rb
      * app/controllers/users/**/*.rb
      
      Partially addresses #47424.
      12ee2753
  37. 24 Sep, 2018 2 commits
  38. 12 Sep, 2018 1 commit