An error occurred fetching the project authors.
- 28 Aug, 2019 1 commit
-
-
Igor authored
- Extract MR fields for notes into a separate serializer - Check if pipelines are empty via count
-
- 21 Aug, 2019 1 commit
-
-
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).
-
- 05 Jul, 2019 1 commit
-
-
drew cimino authored
MergeRequest#all_pipelines fetches Ci::Pipeline records from the source project, so we should specifically check that project for permissions. This was already happening for intra-project merge requests, but in the event that the target and source projects both have private builds, we should ensure that the project permissions are respected.
-
- 04 Jul, 2019 1 commit
-
-
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.
-
- 28 Jun, 2019 1 commit
-
-
Igor Drozdov authored
This commits extracts /merge_requests/1.json?serializer=widget Into a separate /merge_requests/1/widget.json endpoint This will allow to use caching for this request
-
- 22 Jun, 2019 1 commit
-
-
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.
-
- 20 Jun, 2019 1 commit
-
-
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.
-
- 12 Jun, 2019 1 commit
-
-
Shinya Maeda authored
Currently, merge options is updated on #execute method, however, we should have #update interface to make it explicit.
-
- 11 Jun, 2019 1 commit
-
-
Oswaldo Ferreira authored
-
- 03 Jun, 2019 1 commit
-
-
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
-
- 31 May, 2019 1 commit
-
-
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.
-
- 16 Apr, 2019 1 commit
-
-
Matija Čupić authored
This backports the changes from https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/10452
-
- 04 Apr, 2019 1 commit
-
-
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.
-
- 27 Mar, 2019 1 commit
-
-
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
-
- 26 Mar, 2019 1 commit
-
-
Phil Hughes authored
-
- 18 Mar, 2019 1 commit
-
-
Phil Hughes authored
-
- 06 Mar, 2019 1 commit
-
-
Phil Hughes authored
The user can also toggle between the diff changes and the full file diff. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/19054
-
- 08 Feb, 2019 1 commit
-
-
Phil Hughes authored
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/57403
-
- 06 Feb, 2019 1 commit
-
-
Luke Duncalfe authored
-
- 05 Feb, 2019 1 commit
-
-
Rubén Dávila authored
In order to have an accurate date about the last activity of a User we need to update the last_activity_on field when the User is visiting some basic pages of GitLab like pages related to Dashboards, Projects, Issues and Merge Requests
-
- 28 Jan, 2019 1 commit
-
-
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
-
- 24 Jan, 2019 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 21 Dec, 2018 1 commit
-
-
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.
-
- 19 Dec, 2018 1 commit
-
-
Heinrich Lee Yu authored
-
- 07 Dec, 2018 1 commit
-
-
Nick Thomas authored
-
- 06 Dec, 2018 2 commits
-
-
Akos Gyimesi authored
Also, the error message became shorter.
-
Akos Gyimesi authored
-
- 23 Nov, 2018 1 commit
-
-
Jasper Maes authored
-
- 12 Nov, 2018 1 commit
-
-
Filipa Lacerda authored
-
- 31 Oct, 2018 1 commit
-
-
Filipa Lacerda authored
-
- 29 Oct, 2018 1 commit
-
-
Alessio Caiazza authored
-
- 26 Oct, 2018 1 commit
-
-
Sean McGivern authored
Move access checks to their own method so they can be overridden, and port an EE-only method to exist in CE too, with an EE-specific override.
-
- 22 Oct, 2018 1 commit
-
-
Filipa Lacerda authored
-
- 18 Oct, 2018 1 commit
-
-
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.
-
- 05 Oct, 2018 1 commit
-
-
Oswaldo Ferreira authored
-
- 04 Oct, 2018 1 commit
-
-
Brett Walker authored
-
- 26 Sep, 2018 1 commit
-
-
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.
-
- 24 Sep, 2018 2 commits
-
-
Tiago Botelho authored
-
Tiago Botelho authored
-
- 12 Sep, 2018 1 commit
-
-
Alin Ciciu authored
-