18 Jun, 2014

1 commit


15 Jun, 2014

1 commit


13 Jun, 2014

1 commit


10 Jun, 2014

2 commits

  • * send a ‘In-Reply-To’ header along the ‘References’ header
    * subject of answers to an existing thread begins with ‘Re: ’
    
    This fixes threading with at least Mail.app and Airmail.
    Pierre de La Morinerie
     
  • This fixes email threading in Mail.app, that doesn't like when a thread
    doesn't have stable recipients.
    
    For instance, here is a possible sender-recipient combinations before:
    
    From: A
    To: Me
    New issue
    
    From: B
    To: Me
    Reply on new issue
    
    From: A
    To: Me
    Another reply
    
    Mail.app doesn't see B as a participant to the original email thread,
    and decides to break the thread: it will group all messages from A
    together, and separately all messages from B.
    
    This commit makes the thread look like this:
    
    From: A
    To: gitlab/project
    Cc: Me
    New issue
    
    From: B
    To: gitlab/project
    Cc: Me
    Reply on new issue
    
    From: A
    To: gitlab/project
    Cc: Me
    Another reply
    
    Mail.app sees a common recipient, and group the thread correctly.
    Pierre de La Morinerie
     

13 May, 2014

1 commit


09 May, 2014

1 commit


05 May, 2014

1 commit


11 Apr, 2014

1 commit


24 Mar, 2014

1 commit


03 Mar, 2014

3 commits


25 Feb, 2014

1 commit


19 Feb, 2014

2 commits

  • 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
     
  • This changes email subjects from:
    
        GitLab | Team / Project | Note for issue #1234
    
    to:
    
        Team / Project | Note for issue #1234
    
    Rationale:
    
    * Emails should be as meaningful as possible, and emphasize content over
    chrome. The "GitLab" name is more chrome than content.
    
    * Users can tell an email coming from GitLab by the sender or the header
    in the email content.
    
    * An organization that works mainly with GitLab knows that
    every SVC email comes from GitLab. For these organizations, having
    "GitLab" in front of every email is just noise hiding the meaningful
    information.
    Pierre de La Morinerie
     

13 Feb, 2014

1 commit

  • 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
     

22 Jan, 2014

1 commit


18 Dec, 2013

1 commit


08 Nov, 2013

3 commits


08 Oct, 2013

1 commit


12 Sep, 2013

1 commit


26 Aug, 2013

1 commit


22 Aug, 2013

1 commit


20 Aug, 2013

1 commit


17 Jul, 2013

1 commit

  • The good:
    
     - You can do a merge request for a forked commit and it will merge properly (i.e. it does work).
     - Push events take into account merge requests on forked projects
     - Tests around merge_actions now present, spinach, and other rspec tests
     - Satellites now clean themselves up rather then recreate
    
    The questionable:
    
     - Events only know about target projects
     - Project's merge requests only hold on to MR's where they are the target
     - All operations performed in the satellite
    
    The bad:
    
      -  Duplication between project's repositories and satellites (e.g. commits_between)
    
    (for reference: http://feedback.gitlab.com/forums/176466-general/suggestions/3456722-merge-requests-between-projects-repos)
    
    Fixes:
    
    Make test repos/satellites only create when needed
    -Spinach/Rspec now only initialize test directory, and setup stubs (things that are relatively cheap)
    -project_with_code, source_project_with_code, and target_project_with_code now create/destroy their repos individually
    -fixed remote removal
    -How to merge renders properly
    -Update emails to show project/branches
    -Edit MR doesn't set target branch
    -Fix some failures on editing/creating merge requests, added a test
    -Added back a test around merge request observer
    -Clean up project_transfer_spec, Remove duplicate enable/disable observers
    -Ensure satellite lock files are cleaned up, Attempted to add some testing around these as well
    -Signifant speed ups for tests
    -Update formatting ordering in notes_on_merge_requests
    -Remove wiki schema update
    Fixes for search/search results
    -Search results was using by_project for a list of projects, updated this to use in_projects
    -updated search results to reference the correct (target) project
    -udpated search results to print both sides of the merge request
    
    Change-Id: I19407990a0950945cc95d62089cbcc6262dab1a8
    Izaak Alpert
     

24 Jun, 2013

1 commit


22 Jun, 2013

1 commit


14 Jun, 2013

1 commit


01 Apr, 2013

1 commit


28 Mar, 2013

1 commit


19 Mar, 2013

2 commits


01 Feb, 2013

1 commit


18 Jan, 2013

1 commit


15 Jan, 2013

1 commit


31 Dec, 2012

1 commit


23 Nov, 2012

1 commit