- 07 Dec, 2015 2 commits
-
-
Robert Speicher authored
-
Grzegorz Bizon authored
-
- 05 Dec, 2015 1 commit
-
-
Grzegorz Bizon authored
-
- 03 Dec, 2015 4 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
- 21 Nov, 2015 1 commit
-
-
Robert Schilling authored
-
- 19 Nov, 2015 2 commits
-
-
Valery Sizov authored
-
Valery Sizov authored
-
- 18 Nov, 2015 2 commits
-
-
Valery Sizov authored
-
Valery Sizov authored
-
- 15 Oct, 2015 5 commits
-
-
Yorick Peterse authored
-
Yorick Peterse authored
-
Yorick Peterse authored
This ensures that when viewing an issue each note already has the associated project, project members, group and group members available. Since this information is requres for every note this results in quite the reduction of SQL queries being executed.
-
Yorick Peterse authored
-
Yorick Peterse authored
This ensures we don't end up running N+1 queries for the objects in the affected collections.
-
- 14 Oct, 2015 1 commit
-
-
Douwe Maan authored
-
- 12 Oct, 2015 2 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
- 30 Sep, 2015 1 commit
-
-
Robert Speicher authored
-
- 06 Sep, 2015 1 commit
-
-
Stan Hu authored
-
- 19 Aug, 2015 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 12 Aug, 2015 1 commit
-
-
Ben Boeckel authored
This reverts commit 4c586dc7.
-
- 05 Aug, 2015 1 commit
-
-
Valery Sizov authored
This reverts commit fbdaf0e2.
-
- 30 Jul, 2015 1 commit
-
-
Douwe Maan authored
-
- 14 Jul, 2015 1 commit
-
-
Robert Speicher authored
-
- 22 Jun, 2015 1 commit
-
-
Robert Speicher authored
-
- 05 Jun, 2015 1 commit
-
-
Jeroen van Baarsen authored
**What does this do?** It makes sure that whenever a new note is added to an noteable item, the updated_at of that item is also updated. **Why is this needed?** At this moment when you post a comment on an issue or add a label to an issue, the updated_at is not changed. Because of this the filtering for least recently updated is not really useful (since it only takes in account the original text from the noteable). Signed-off-by: Jeroen van Baarsen <jeroenvanbaarsen@gmail.com>
-
- 26 May, 2015 1 commit
-
-
Robert Speicher authored
-
- 11 May, 2015 3 commits
-
-
Robert Speicher authored
-
Robert Speicher authored
There's a lot of code in the Note model that only deals with creating system notes, so we're going to split that into its own class.
-
Robert Speicher authored
-
- 24 Apr, 2015 5 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
- 16 Apr, 2015 1 commit
-
-
Robert Speicher authored
-
- 15 Apr, 2015 1 commit
-
-
Dominik Sander authored
Having a merge request with a comments on a line which is then changed in a later commit prevented new comments from properly showing up in the merge request show page. * `Note#set_diff` do not use stored the diff when creating a new note in merge requests (we can not be sure the diff did not changed since the last comment on that line) * Do not rely just on `outdated?` of the first note when displaying comments of a MR in the discussion tab, but partition the active/outdated notes and display them all * In the inline changes tab just select the active notes, so an outdated note does not prevent an active one from being rendered * Just show active comments in the side-by-side changes tab
-