delta/gitlab/gitlab-ce.git/spec/fixtures/emails, branch docs/fix-commit-api-render

Use new issue email address format

2019-01-03T20:37:35+00:00

We now use `-issue` in order to support catch all email addresses

Use new merge request email address format

2019-01-03T20:37:35+00:00

We now use `-merge-request` instead of `+merge-request+`
in order to support catch all email addresses

Eliminate duplicated words

2018-11-21T16:01:23+00:00

Signed-off-by: Takuya Noguchi

Apply patches when creating MR via email

2018-11-07T15:27:55+00:00

This allows users to add patches as attachments to merge request
created via email.

When an email to create a merge request is sent, all the attachments
ending in `.patch` will be applied to the branch specified in the
subject of the email. If the branch did not exist, it will be created
from the HEAD of the repository.

When the patches could not be applied, the error message will be
replied to the user.

The patches can have a maximum combined size of 2MB for now.

Put fallback reply-key address first in the References header

2018-07-27T13:12:52+00:00

The References header is an ordered list of mails, and some clients
only look at the last mail in the list to determine to which mail the
mail is in reply to.

Therefore, to be a less obtrusive as possible, put the fallback
address first.

Some info about the reply key lookup in the References header:
https://docs.gitlab.com/ee/administration/reply_by_email.html#how-it-works

skip email trim when email is creating new issue

2018-05-23T04:05:51+00:00

Updates from MR discussion

1. Added test for ReplyParser
2. Changed param to trim_reply with default set as true

Removed keyword param in favor of normal options param

updates for MR discussion

Resolutions for code review comments

more code review fixes

Fix quick actions for users who cannot update issues and MRs

2018-03-02T16:16:13+00:00

There are several quick actions now that don't need this access - /todo and
/unsubscribe for instance - but when these were first added, there
weren't. Quick actions are now responsible for checking their own permissions.

Default to HTTPS for all Gravatar URLs

2018-01-25T09:00:46+00:00

If using gravatar.com, both plain_url and ssl_url in settings are now
served via HTTPS. Make this the default.

Use message body for merge request description

2017-12-11T10:46:21+00:00

When a merge request is created from email, use message body
as merge request description. If message body is empty then
merge request description is still created from the source
branch commit (if there is only single commit in the merge
request).

If message body is empty and there are multiple commits in
the source branch, then merge request description is left empty.

Closes #40968

Create merge request from email

2017-12-05T07:41:58+00:00

* new merge request can be created by sending an email to the specific
email address (similar to creating issues by email)
* for the first iteration, source branch must be specified in the mail
subject, other merge request parameters can not be set yet
* user should enable "Receive notifications about your own activity" in
user settings to receive a notification about created merge request

Part of #32878