Software Publico / Gitlab

03 Mar, 2014

3 commits

eeb011e3 Remove the author name from issue notes emails ... Browse File »
```
Rationale: the author name is now displayed in the email "From" field;
this information is no longer needed.
```
Pierre de La Morinerie
2014-03-03 16:58:44 +0100
8e421d2b Add the description to the "new issue" and "new merge request" emails ... Browse File »
```
Previously the content of the issue or merge request was missing from
the email.
```
Pierre de La Morinerie
2014-03-03 16:58:44 +0100

7ba0b502 Add a "View in GitLab" link in notification emails ... Browse File »

When an email notification concerns a specific object (issue, note,
merge request, etc.), add a link to the footer of the email that opens
the item's page in a web browser.

Rationale:

* The link is predictable: always the same text, always at the same
location, like any reliable tool.

* It allows to remove the inline-title in many emails, and leave only
the actual content of the message.

2014-03-03 16:58:44 +0100

25 Feb, 2014

1 commit

ffce379a Fix email test ... Browse File »
```
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
```
Dmitriy Zaporozhets
2014-02-25 17:49:20 +0200

19 Feb, 2014

2 commits

96dded3e Send emails from the author ... Browse File »

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.

2014-02-19 18:25:18 +0100

44ab156e Remove the email subject prefix ... Browse File »

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.

2014-02-19 18:25:18 +0100

13 Feb, 2014

1 commit

29cfd33d Add email aliases for users ... Browse File »

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.

2014-02-13 22:59:39 -0600

22 Jan, 2014

1 commit

c227aa44 Make changes to tests ... Browse File »

* project_with_code -> project
* project -> ermpty_project

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

2014-01-22 21:03:52 +0200

18 Dec, 2013

1 commit

fc3878c0 Email on push mailer spec ... Browse File »
```
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
```
Dmitriy Zaporozhets
2013-12-18 13:30:04 +0200

08 Nov, 2013

3 commits

ea3680ad Merge pull request #5571 from bke-drewb/email ... Browse File »
```
Fix minor errors/annoyances in email templates
```
Dmitriy Zaporozhets
2013-11-08 23:59:27 -0800
4b98597e Add specs for Email confirmation ... Browse File »
```
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
```
Dmitriy Zaporozhets
2013-11-08 18:29:26 +0200

57ad81a9 Fix minor errors/annoyances in email templates ... Browse File »

There was some funny syntax in merge request email templates. There was a ! before
the merge request number when there probably should be a #. This may be some carry over
from markdown but should not be in email templates.  There were also some capitalization
discrepancies among the subject lines. For those OCD people out there I standardized the
capitalization. :)

2013-11-08 10:20:15 -0600

08 Oct, 2013

1 commit

903090d1 Fix the sigil for merge request emails Browse File »

Abe Hassan
2013-10-08 11:32:26 -0700

12 Sep, 2013

1 commit

c1dd31cf Enable UsersGroup observer, Add group_member methods to NotificationService Browse File »

Dmitriy Zaporozhets
2013-09-12 19:00:32 +0300

26 Aug, 2013

1 commit

a7bd18f9 Fix mailer tests Browse File »

Dmitriy Zaporozhets
2013-08-26 20:58:34 +0300

22 Aug, 2013

1 commit

0fcd89e3 Show iids for issues/mr in email subject Browse File »

Dmitriy Zaporozhets
2013-08-22 15:40:48 +0300

20 Aug, 2013

1 commit

7a26a4b6 Refactor access roles methods Browse File »

Dmitriy Zaporozhets
2013-08-20 15:59:45 +0300

17 Jul, 2013

1 commit

3d7194f0 Merge Request on forked projects ... Browse File »

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