An error occurred fetching the project authors.
- 08 Jun, 2016 1 commit
-
-
Alejandro Rodríguez authored
`notes_with_associations` are used for `participant` declarations, but `Participable` only really cares about the target entity project, and not the participants projects. `notes_with_associations` are also used in `Commit::has_been_reverted?` which employs the reference extractor of the commit, so no references to the notes projects are made there (`Mentionable::all_references` cares only about the `author` and other `attr_mentionable`). A paralel situation occurs on `Issue::referenced_merge_requests`.
-
- 02 Jun, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 01 Jun, 2016 1 commit
-
-
Yorick Peterse authored
There are several changes to this module: 1. The use of an explicit stack in Participable#participants 2. Proc behaviour has been changed 3. Batch permissions checking == Explicit Stack Participable#participants no longer uses recursion to process "self" and all child objects, instead it uses an Array and processes objects in breadth-first order. This allows us to for example create a single Gitlab::ReferenceExtractor instance and pass this to any Procs. Re-using a ReferenceExtractor removes the need for running potentially many SQL queries every time a Proc is called on a new object. == Proc Behaviour Changed Previously a Proc in Participable was expected to return an Array of User instances. This has been changed and instead it's now expected that a Proc modifies the Gitlab::ReferenceExtractor passed to it. The return value of the Proc is ignored. == Permissions Checking The method Participable#participants uses Ability.users_that_can_read_project to check if the returned users have access to the project of "self" _without_ running multiple SQL queries for every user.
-
- 19 Apr, 2016 2 commits
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 18 Apr, 2016 1 commit
-
-
P.S.V.R authored
Issue: https://gitlab.com/gitlab-org/gitlab-ce/issues/12785 Merge Request: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3514
-
- 13 Apr, 2016 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 11 Apr, 2016 2 commits
-
-
Felipe Artur authored
-
Kamil Trzcinski authored
-
- 01 Apr, 2016 1 commit
-
-
Yorick Peterse authored
These methods are called quite often in loops so by memoizing their output we can reduce timings a bit.
-
- 22 Mar, 2016 1 commit
-
-
Rubén Dávila authored
-
- 03 Mar, 2016 1 commit
-
-
Jacob Vosmaer authored
-
- 22 Feb, 2016 1 commit
-
-
Rémy Coutable authored
-
- 19 Feb, 2016 12 commits
-
-
Rubén Dávila authored
-
Rubén Dávila authored
-
Rubén Dávila authored
-
Rubén Dávila authored
-
Rubén Dávila authored
-
Rubén Dávila authored
* Now it's only created when user choose to create a MR and logic to hide it is handled by https://gitlab.com/gitlab-org/gitlab-ce/blob/50595af7b0e304f16e2955109abd2d25cd96efda/app/helpers/application_helper.rb#L139
-
Rubén Dávila authored
-
Rubén Dávila authored
-
Rubén Dávila authored
-
Rubén Dávila authored
-
Rubén Dávila authored
-
Rubén Dávila authored
-
- 30 Jan, 2016 1 commit
-
-
Robert Speicher authored
This is the git default and will help to prevent false positive matches. Closes #12706
-
- 09 Dec, 2015 1 commit
-
-
Rubén Dávila authored
-
- 07 Dec, 2015 2 commits
-
-
Valery Sizov authored
-
Valery Sizov authored
-
- 04 Dec, 2015 1 commit
-
-
Valery Sizov authored
-
- 01 Dec, 2015 2 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
- 30 Nov, 2015 1 commit
-
-
Douwe Maan authored
-
- 22 Oct, 2015 1 commit
-
-
Douwe Maan authored
-
- 20 Oct, 2015 1 commit
-
-
Douwe Maan authored
-
- 14 Oct, 2015 1 commit
-
-
Douwe Maan authored
-
- 12 Oct, 2015 1 commit
-
-
Kamil Trzcinski authored
-
- 23 Jun, 2015 1 commit
-
-
Robert Speicher authored
- Removes looking up authors/committers by name - Renames `User.find_for_commit` to `User.find_by_any_email`
-
- 10 Jun, 2015 1 commit
-
-
Robert Speicher authored
As of Ruby 1.9, this is the correct way to handle `respond_to?` for methods implemented by `method_missing`. See https://robots.thoughtbot.com/always-define-respond-to-missing-when-overriding
-
- 26 May, 2015 1 commit
-
-
Robert Speicher authored
-