An error occurred fetching the project authors.
- 02 Nov, 2018 1 commit
-
-
Chantal Rollison authored
-
- 23 Oct, 2018 1 commit
-
-
Sean McGivern authored
-
- 24 Sep, 2018 2 commits
-
-
Tiago Botelho authored
-
Tiago Botelho authored
-
- 11 Sep, 2018 2 commits
-
-
Yorick Peterse authored
This whitelists all existing offenses for the various CodeReuse cops, of which most are triggered by the CodeReuse/ActiveRecord cop.
-
Yorick Peterse authored
This whitelists all existing offenses for the various CodeReuse cops, of which most are triggered by the CodeReuse/ActiveRecord cop.
-
- 15 Aug, 2018 1 commit
-
-
gfyoung authored
-
- 20 Jun, 2018 1 commit
-
-
Mark Chao authored
There is still the edge case when 'no commits' changes to 'conflict' would not trigger notification, which we ignore for now. Calling can_be_merged? can cause exception (e.g. non-UTF8) Ignore those by rescueing. Remove unmergeable_reason as now only conflict is notified Update spec
-
- 24 May, 2018 1 commit
-
-
Mark Chao authored
-
- 18 May, 2018 2 commits
- 17 May, 2018 2 commits
- 03 Apr, 2018 1 commit
-
-
Sean McGivern authored
This was sending the current user, which is the recipient! It should be the user who pushed the commits.
-
- 26 Mar, 2018 1 commit
-
-
YarNayar authored
Closes #23460
-
- 19 Jan, 2018 1 commit
-
-
Luke Bennett authored
-
- 18 Jan, 2018 1 commit
-
-
Mario de la Ossa authored
Adds `#build_notification_recipients` to `NotificationRecipientService` that returns the `NotificationRecipient` objects in order to be able to access the new attribute `reason`. This new attribute is used in the different notifier methods in order to add the reason as a header: `X-GitLab-NotificationReason`. Only the reason with the most priority gets sent.
-
- 17 Jan, 2018 1 commit
-
-
Mario de la Ossa authored
Adds `#build_notification_recipients` to `NotificationRecipientService` that returns the `NotificationRecipient` objects in order to be able to access the new attribute `reason`. This new attribute is used in the different notifier methods in order to add the reason as a header: `X-GitLab-NotificationReason`. Only the reason with the most priority gets sent.
-
- 05 Jul, 2017 2 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
- 17 Jan, 2017 3 commits
-
-
Sean McGivern authored
-
Sean McGivern authored
-
Sean McGivern authored
-
- 16 Jan, 2017 1 commit
-
-
Sean McGivern authored
-
- 19 Aug, 2016 1 commit
-
-
Douwe Maan authored
Diff line comments resolve ## What does this MR do? Diff line comments can be resolved. Part of #10325 To do: - [x] Backend (@DouweM) - [x] Fix https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5022#note_13319326. Will be made easier by https://gitlab.com/gitlab-org/gitlab-ce/issues/17237#note_13370331 - [x] System note when all discussions are resolved - [x] Notification when all discussions are resolved - [x] Write unit tests - [x] Look at resolve time https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5022#note_13912743 - Fixed by 4a13aa9f - [x] Frontend (@iamphill) - [x] Fix bugs - [x] Write more feature tests - [x] Frontend (@connorshea) - [x] Address frontend feedback - [x] Feature specs for Jump feature - [x] Documentation - [x] Add Vue.js in a standard way See merge request !5022
-
- 17 Aug, 2016 1 commit
-
-
Robert Speicher authored
Send notification emails when users are newly mentioned in issue or MR edits ## What does this MR do? Introduces "new mention in issue" and "new mention in MR" email notifications. Editing a Mentionable title or description and adding a mention to a user who was not previously mentioned will now send them a notification email, following usual permissions for doing so. ## Why was this MR needed? Issues & MRs may be edited to include mentions to new people. We don't currently send out email notifications of these edits to anyone, although they do create TODOs. This brings email notifications into parity with TODOs. ## What are the relevant issue numbers? Closes #2451 See merge request !5800
-
- 15 Aug, 2016 1 commit
-
-
Nick Thomas authored
-
- 29 Jul, 2016 1 commit
-
-
Douwe Maan authored
-
- 12 Jul, 2016 1 commit
-
-
Sean McGivern authored
When an approver is added to an MR, create a todo for them and send them an email.
-
- 20 Jun, 2016 1 commit
-
-
Sean McGivern authored
-
- 19 Apr, 2016 1 commit
-
-
Ben Bodenmiller authored
-
- 15 Mar, 2016 3 commits
-
-
Rémy Coutable authored
-
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.
-
- 15 Jan, 2016 1 commit
-
-
Robert Speicher authored
-
- 09 Jan, 2016 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 19 Aug, 2015 2 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
- 18 Aug, 2015 1 commit
-
-
Douwe Maan authored
-
- 14 Feb, 2015 1 commit
-
-
Vinnie Okada authored
Make the following changes to deal with new behavior in Rails 4.1.2: * Use nested resources to avoid slashes in arguments to path helpers.
-