An error occurred fetching the project authors.
- 01 Feb, 2018 1 commit
-
-
Yorick Peterse authored
This ensures that we have more visibility in the number of SQL queries that are executed in web requests. The current threshold is hardcoded to 100 as we will rarely (maybe once or twice) change it. In production and development we use Sentry if enabled, in the test environment we raise an error. This feature is also only enabled in production/staging when running on GitLab.com as it's not very useful to other users.
-
- 10 Jan, 2018 1 commit
-
-
Tony Rom authored
-
- 05 Jan, 2018 1 commit
-
-
Brent Greeff authored
-
- 20 Dec, 2017 2 commits
-
-
Mark Fletcher authored
-
Mark Fletcher authored
- Ensure that unwanted params are no passed to actual finder classes
-
- 15 Dec, 2017 1 commit
-
-
Tony Rom authored
-
- 25 Nov, 2017 1 commit
-
-
George Andrinopoulos authored
-
- 23 Nov, 2017 1 commit
-
-
Sean McGivern authored
Compared to the merge_request_diff association: 1. It's simpler to query. The query uses a foreign key to the merge_request_diffs table, so no ordering is necessary. 2. It's faster for preloading. The merge_request_diff association has to load every diff for the MRs in the set, then discard all but the most recent for each. This association means that Rails can just query for N diffs from N MRs. 3. It's more complicated to update. This is a bidirectional foreign key, so we need to update two tables when adding a diff record. This also means we need to handle this as a special case when importing a GitLab project. There is some juggling with this association in the merge request model: * `MergeRequest#latest_merge_request_diff` is _always_ the latest diff. * `MergeRequest#merge_request_diff` reuses `MergeRequest#latest_merge_request_diff` unless: * Arguments are passed. These are typically to force-reload the association. * It doesn't exist. That means we might be trying to implicitly create a diff. This only seems to happen in specs. * The association is already loaded. This is important for the reasons explained in the comment, which I'll reiterate here: if we a) load a non-latest diff, then b) get its `merge_request`, then c) get that MR's `merge_request_diff`, we should get the diff we loaded in c), even though that's not the latest diff. Basically, `MergeRequest#merge_request_diff` is the latest diff in most cases, but not quite all.
-
- 30 Oct, 2017 1 commit
-
-
Mark Fletcher authored
-
- 05 Oct, 2017 1 commit
-
-
Vitaliy @blackst0ne Klachkov authored
-
- 18 Sep, 2017 1 commit
-
-
haseeb authored
-
- 14 Sep, 2017 1 commit
-
-
Jarka Kadlecova authored
-
- 05 Sep, 2017 1 commit
-
-
Hiroyuki Sato authored
-
- 31 Aug, 2017 1 commit
-
-
Robert Schilling authored
-
- 29 Aug, 2017 1 commit
-
-
Travis Miller authored
-
- 28 Aug, 2017 2 commits
-
-
Robert Schilling authored
-
Robert Schilling authored
-
- 27 Jul, 2017 2 commits
-
-
Toon Claes authored
This matches the behavior of the /issues endpoint.
-
Toon Claes authored
And add support for additional query parameters: - `author_id`: Returns merge requests created by the given user `id` - `assignee_id`: Returns merge requests assigned to the given user `id` - `scope`: Return merge requests for the given scope: `created-by-me`, `assigned-to-me` or `all`
-
- 24 Jul, 2017 1 commit
-
-
Jarka Kadlecova authored
-
- 20 Jul, 2017 1 commit
-
-
Dmitriy Zaporozhets authored
New version of the gem returns 200 status code on delete with content instead of 204 so we explicitly set status code to keep existing behavior Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 11 Jul, 2017 2 commits
- 10 Jul, 2017 2 commits
- 09 Jul, 2017 1 commit
-
-
Stan Hu authored
Closes #34159
-
- 07 Jul, 2017 1 commit
-
-
Stan Hu authored
Identified via `ENABLE_BULLET=1 bundle exec rspec spec/requests/api/merge_requests_spec.rb:34` Improves speed of #34159
-
- 18 Jun, 2017 1 commit
-
-
Kyle Bishop authored
-
- 16 Jun, 2017 1 commit
-
-
Felipe Artur authored
-
- 26 Apr, 2017 1 commit
-
-
mhasbini authored
-
- 25 Apr, 2017 1 commit
-
-
Robert Schilling authored
-
- 24 Apr, 2017 1 commit
-
-
Chris Wilson authored
When updating a merge request via the `/merge` endpoint we check the `mergeable` and `mergeable_state` status, these will return `false` if the application option only_allow_merge_if_pipeline_succeeds is enabled. We should skip CI checks if the request uses the merge_when_pipeline_succeeds param Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/22740
-
- 10 Apr, 2017 1 commit
-
-
Oswaldo Ferreira authored
-
- 27 Mar, 2017 1 commit
-
-
Toon Claes authored
Comments for a merge request should be obtained to the `notes` endpoint.
-
- 16 Mar, 2017 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 07 Mar, 2017 1 commit
-
-
Timothy Andrew authored
- As opposed to the `id` that was previously being used. - This brings the API routes closer to the web interface's routes. - This is specific to API v4.
-
- 06 Mar, 2017 1 commit
-
-
Adam Niedzielski authored
-
- 01 Mar, 2017 1 commit
-
-
James Lopez authored
Rename column in the database Rename fields related to import/export feature Rename API endpoints Rename documentation links Rename the rest of occurrences in the code Replace the images that contain the words "build succeeds" and docs referencing to them Make sure pipeline is green and nothing is missing. updated doc images renamed only_allow_merge_if_build_succeeds in projects and fixed references more updates fix some spec failures fix rubocop offences fix v3 api spec fix MR specs fixed issues with partials fix MR spec fix alignment add missing v3 to v4 doc wip - refactor v3 endpoints fix specs fix a few typos fix project specs copy entities fully to V3 fix entity error more fixes fix failing specs fixed missing entities in V3 API remove comment updated code based on feedback typo fix spec
-
- 23 Feb, 2017 2 commits
-
-
Douwe Maan authored
This reverts commit e00fb2bdc2090e9cabeb1eb35a2672a882cc96e9. # Conflicts: # .rubocop.yml # .rubocop_todo.yml # lib/gitlab/ci/config/entry/global.rb # lib/gitlab/ci/config/entry/jobs.rb # spec/lib/gitlab/ci/config/entry/factory_spec.rb # spec/lib/gitlab/ci/config/entry/global_spec.rb # spec/lib/gitlab/ci/config/entry/job_spec.rb # spec/lib/gitlab/ci/status/build/factory_spec.rb # spec/lib/gitlab/incoming_email_spec.rb
-
Douwe Maan authored
This reverts commit cb10b725c8929b8b4460f89c9d96c773af39ba6b.
-