- 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 2 commits
-
-
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
-
Douwe Maan authored
-
- 02 Apr, 2015 1 commit
-
-
Stan Hu authored
Fix bug where error messages from Dropzone would not be displayed on the issues page Closes #1258
-
- 23 Mar, 2015 1 commit
-
-
Douwe Maan authored
-
- 19 Mar, 2015 1 commit
-
-
Stan Hu authored
Remove emphasis from system notes to avoid Markdown conflicts in names.
-
- 18 Mar, 2015 3 commits
-
-
Dmitriy Zaporozhets authored
This reverts commit 7602cef5.
-
Samuel Bernard authored
-
Douwe Maan authored
-
- 06 Mar, 2015 3 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
Stan Hu authored
Supports four different event types all bundled under the "note" event type: - comments on a commit - comments on an issue - comments on a merge request - comments on a code snippet
-
- 20 Feb, 2015 1 commit
-
-
Douwe Maan authored
-
- 08 Feb, 2015 1 commit
-
-
Nikita Verkhovin authored
-
- 06 Feb, 2015 2 commits
-
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
- 05 Feb, 2015 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 22 Jan, 2015 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 19 Jan, 2015 1 commit
-
-
Michael Clarke authored
-
- 18 Jan, 2015 1 commit
-
-
Steven Burgart authored
signe-in -> signed-in go_to_gihub_for_permissions -> go_to_github_for_permissions descendand -> descendant behavour -> behaviour recepient_email -> recipient_email generate_fingerpint -> generate_fingerprint dependes -> depends Cant't -> Can't wisit -> visit notifcation -> notification sufficent_scope -> sufficient_scope? levet -> level
-
- 11 Jan, 2015 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 15 Dec, 2014 1 commit
-
-
Dmitriy Zaporozhets authored
In some strange cases Ruby thinks `system` is not AR field but Kernel.system call and raises exception during save. It should prevent this random wierd behaviour Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-