An error occurred fetching the project authors.
- 02 Jun, 2016 4 commits
-
-
Paco Guzman authored
This will be useful when you want to ask for the number of items and later iterate over them, without needing to ask if the association is load or not. So you avoid extra database queries
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
Josh Frye authored
-
Josh Frye authored
-
- 01 Jun, 2016 2 commits
-
-
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.
-
Z.J. van de Weg authored
-
- 31 May, 2016 2 commits
-
-
Felipe Artur authored
-
Felipe Artur authored
-
- 24 May, 2016 5 commits
-
-
Felipe Artur authored
-
Felipe Artur authored
-
Felipe Artur authored
-
Felipe Artur authored
-
Felipe Artur authored
-
- 12 May, 2016 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 10 May, 2016 1 commit
-
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- 09 May, 2016 1 commit
-
-
cnam-dep authored
-
- 06 May, 2016 2 commits
-
-
Takuya Noguchi authored
-
Zeger-Jan van de Weg authored
-
- 20 Apr, 2016 5 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>
-
Mehmet Beydogan authored
Fix typos on sorting dropdown related to due date Remove constant array and add Structs on Issue to keep due date data to fill options
-
Mehmet Beydogan authored
Add due_date text field to sidebar issue#show Add ability sorting issues by due date ASC and DESC Add ability to filtering issues by No Due Date, Any Due Date, Due to tomorrow, Due in this week options Add handling issue due_date field for MergeRequest Update CHANGELOG Fix ambigous match for issues#show sidebar Fix SCREAMING_SNAKE_CASE offenses for due date contants Add specs for due date sorting and filtering on issues
-
James Lopez authored
-
- 19 Apr, 2016 1 commit
-
-
James Lopez authored
-
- 02 Apr, 2016 1 commit
-
-
Rubén Dávila authored
This problem only was affecting the dev env.
-
- 30 Mar, 2016 1 commit
-
-
Douglas Barbosa Alexandre authored
-
- 21 Mar, 2016 1 commit
-
-
Douglas Barbosa Alexandre authored
The `non_archived` scope applied here https://gitlab.com/gitlab-org/gitlab-ce/blob/master/app/controllers/conc erns/issues_action.rb#L5 overrides the previous `ORDER BY` applied inside the IssuesFinder, with the default scope of the Project model, resulting in SQL errors.
-
- 19 Mar, 2016 2 commits
-
-
Zeger-Jan van de Weg authored
-
Grzegorz Bizon authored
According to endbosses' suggestions.
-
- 15 Mar, 2016 2 commits
-
-
Rémy Coutable authored
1. Make the "subscribed" text in Issuable sidebar reflect the labels subscription status 2. Current user mut be logged-in to toggle issue/MR/label subscription
-
Timothy Andrew authored
1. Allow subscribing (the current user) to a label - Refactor the `Subscription` coffeescript class - The main change is that it accepts a container, and conducts all DOM queries within its scope. We need this because the labels page has multiple instances of `Subscription` on the same page. 2. Creating an issue or MR with labels notifies users subscribed to those labels - Label `has_many` subscribers through subscriptions. 3. Adding a label to an issue or MR notifies users subscribed to those labels - This only applies to subscribers of the label that has just been added, not all labels for the issue.
-
- 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
-
- 22 Feb, 2016 2 commits
-
-
Zeger-Jan van de Weg authored
-
Zeger-Jan van de Weg authored
Closes #9014 The only difference with #9014 is that I thoughed the author should also be able to assign the issue. If this is unwanted behavior Ill revert it.
-
- 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.
-