14 Mar, 2014

3 commits

13 Mar, 2014

1 commit

12 Mar, 2014

2 commits

06 Mar, 2014

2 commits

05 Mar, 2014

1 commit

25 Feb, 2014

3 commits

  • 645e8d47   Move services for collecting items to Finders ... Browse Dir » 
    Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
    Dmitriy Zaporozhets
     
  • c3a3f80a   Merge branch 'cleaner-email-headers' into 'master' ... Browse Dir » 
    Cleaner headers in Notification Emails

Make the informations available in the notification email headers (sender, recipient, subject, etc.) more readable and meaningful.

* Remove the email subject prefix
* Don't write the project namespace in email subjects
* Write the issue/merge request title in the notification email subject
* Make the email appear as sent from the action author (the actual email address is still `gitlab@gitlab.com`)

For instance, this is the notification email for a new issue comment before:

> From: gitlab@gitlab.com
> To: myemailaddress@gmail.com
> Subject: GitLab | GitLab HQ / GitLab-Shell | New note for issue #1234

And after :

> From: Nick Brown <gitlab@gitlab.com>
> To: myemailaddress@gmail.com
> Subject: GitLab-Shell |  Add local update hook  (#1234)

The recipient of the notification can easily get the gist of the message without even opening it — just by looking at how it appears in her inbox. None of the actual email addresses (From, To, Reply-to) changes, just the display name.

Having a consistent subject for all notification emails sent about some resource also allow good email clients to group the discussion by thread (although grouping in Mail.app still needs some work).
    Dmitriy Zaporozhets
     
  • 75eed4eb   Implement project collection service ... Browse Dir » 
    Main purpose is move big amount of methods from user, group, project
models and place filtering logic in one place.
It also fixes 500 error on group page for PostgreSQL

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
    Dmitriy Zaporozhets
     

20 Feb, 2014

2 commits

19 Feb, 2014

1 commit

  • 96dded3e   Send emails from the author ... Browse Dir » 
    This changes the email "From" field from "gitlab@example.com" to either:

* "John Doe <gitlab@example.com>" if the author of the action is known,
* "GitLab <gitlab@example.com>" otherwise.

Rationale: this allow mails to appear as if they were sent by the
author. It appears in the mailbox more like a real discussion between
the sender and the receiver ("John sent: we should refactor this") and
less like a robot notifying about something.
    Pierre de La Morinerie
     

13 Feb, 2014

1 commit

  • 29cfd33d   Add email aliases for users ... Browse Dir » 
    Emails are used to associate commits with users. The emails
are not verified and don't have to be valid email addresses. They
are assigned on a first come, first serve basis.

Notifications are sent when an email is added.
    Jason Hollingsworth
     

10 Feb, 2014

1 commit

05 Feb, 2014

3 commits

03 Feb, 2014

2 commits

31 Jan, 2014

1 commit

24 Jan, 2014

1 commit

19 Jan, 2014

1 commit

17 Jan, 2014

1 commit

16 Jan, 2014

4 commits

15 Jan, 2014

5 commits

04 Dec, 2013

1 commit

01 Dec, 2013

1 commit

20 Nov, 2013

1 commit

08 Nov, 2013

1 commit

14 Oct, 2013

1 commit