- 11 Mar, 2016 1 commit
-
-
Yorick Peterse authored
-
- 07 Mar, 2016 1 commit
-
-
Rubén Dávila authored
-
- 05 Mar, 2016 1 commit
-
-
Rubén Dávila authored
Make methods return ActiveRecord Relations instead of Arrays.
-
- 02 Mar, 2016 1 commit
-
-
Rubén Dávila authored
-
- 19 Feb, 2016 2 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
- 17 Feb, 2016 1 commit
-
-
Douglas Barbosa Alexandre authored
-
- 16 Feb, 2016 1 commit
-
-
Rémy Coutable authored
-
- 15 Feb, 2016 1 commit
-
-
Rémy Coutable authored
1. We now display the index of the current issuable among all its project's issuables, of the same type and with the same state. 2. Also, refactored a bit the Issuable helpers into a new IssuablesHelper module. 3. Added acceptance specs for the sidebar counter.
-
- 11 Feb, 2016 1 commit
-
-
Kirill Zaitsev authored
- Add `avatar_url`, `description`, `git_ssh_url`, `git_http_url`, `path_with_namespace` and `default_branch` in `project` in push, issue, merge-request and note webhooks data - Deprecate the `ssh_url` in favor of `git_ssh_url` and `http_url` in favor of `git_http_url` in `project` for push, issue, merge-request and note webhooks data - Deprecate the `repository` key in push, issue, merge-request and note webhooks data, use `project` instead
-
- 10 Feb, 2016 1 commit
-
-
Bram Daams authored
-
- 22 Jan, 2016 1 commit
-
-
Rubén Dávila authored
-
- 20 Jan, 2016 1 commit
-
-
Rubén Dávila authored
-
- 09 Jan, 2016 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 07 Jan, 2016 1 commit
-
-
Yorick Peterse authored
Sorting by "id" has the same effect as sorting by created_at while performing far better and without the need of an extra index (in case one wanted to speed up sorting by "created_at"). Sorting by "Recently updated" still uses the physical "updated_at" column as there's no way to use the "id" column for this instead.
-
- 06 Jan, 2016 1 commit
-
-
Douwe Maan authored
-
- 28 Dec, 2015 1 commit
-
-
Valery Sizov authored
-
- 24 Dec, 2015 2 commits
-
-
Robert Speicher authored
-
Douwe Maan authored
-
- 23 Dec, 2015 3 commits
-
-
Grzegorz Bizon authored
`runners_registration_token` now creates a new token if it is blank.
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
Until now, `ensure_#{token_filed_name}` method didn't persist new token in database. This closes #4235.
-
- 21 Dec, 2015 1 commit
-
-
Douwe Maan authored
-
- 16 Dec, 2015 1 commit
-
-
Douwe Maan authored
-
- 15 Dec, 2015 2 commits
-
-
Douwe Maan authored
-
Gabriel Mazetto authored
-
- 11 Dec, 2015 3 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
This adds a ability to use multiple different authentication token fields in other models. From now on it is necessary to add authentication token field manually in each class that implements this mixin.
-
- 01 Dec, 2015 2 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
- 30 Nov, 2015 2 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
- 26 Nov, 2015 1 commit
-
-
Jose Corcuera authored
-
- 21 Nov, 2015 1 commit
-
-
Robert Schilling authored
-
- 20 Nov, 2015 3 commits
-
-
Rubén Dávila authored
-
Ruben Davila authored
Everytime the User check or uncheck a Task Item from the Issue or Merge Request description, a new update is going to be added to the activity logs of the Issue or Merge Request. Note that when using the edit form, you can only update the Task item status or add/delete/modify existing ones. Doing both actions is not fully supported.
- 19 Nov, 2015 1 commit
-
-
Yorick Peterse authored
When using IssuableFinder/IssuesFinder to find issues for multiple projects it's more efficient to use a JOIN + a "WHERE project_id IN" condition opposed to running a sub-query. This change means that when finding issues without labels we're now using the following SQL: SELECT issues.* FROM issues JOIN projects ON projects.id = issues.project_id LEFT JOIN label_links ON label_links.target_type = 'Issue' AND label_links.target_id = issues.id WHERE ( projects.id IN (...) OR projects.visibility_level IN (20, 10) ) AND issues.state IN ('opened','reopened') AND label_links.id IS NULL ORDER BY issues.id DESC; instead of: SELECT issues.* FROM issues LEFT JOIN label_links ON label_links.target_type = 'Issue' AND label_links.target_id = issues.id WHERE issues.project_id IN ( SELECT id FROM projects WHERE id IN (...) OR visibility_level IN (20,10) ) AND issues.state IN ('opened','reopened') AND label_links.id IS NULL ORDER BY issues.id DESC; The big benefit here is that in the last case PostgreSQL can't properly use all available indexes. In particular it ends up performing a sequence scan on the "label_links" table (processing around 290 000 rows). The new query is roughly 2x as fast as the old query.
-
- 18 Nov, 2015 1 commit
-
-
Valery Sizov authored
-