root
/
gitlab-ce
mirror of https://gitlab.com/free-releases/gitlab-ce.git
1
0
Fork 0
Code Issues Actions Packages Projects Releases Wiki Activity
114,136 Commits 9,131 Branches 1,640 Tags 2 GiB
Commit Graph

52 Commits

Author SHA1 Message Date
GitLab Bot d5d37ee3ca Add latest changes from gitlab-org/gitlab@master 2024-10-24 15:16:35 +00:00
GitLab Bot 72b735b5f2 Add latest changes from gitlab-org/gitlab@master 2024-10-14 18:16:04 +00:00
GitLab Bot 1252510698 Add latest changes from gitlab-org/gitlab@master 2024-10-10 12:16:58 +00:00
GitLab Bot 1cdda1cbfb Add latest changes from gitlab-org/gitlab@master 2024-04-26 12:12:07 +00:00
GitLab Bot 8a74643179 Add latest changes from gitlab-org/gitlab@master 2023-11-14 09:11:08 +00:00
GitLab Bot 774f6e6e98 Add latest changes from gitlab-org/gitlab@master 2023-10-24 21:12:08 +00:00
GitLab Bot 3b260cb69f Add latest changes from gitlab-org/gitlab@master 2023-10-12 12:11:32 +00:00
GitLab Bot 102640e087 Add latest changes from gitlab-org/gitlab@master 2023-07-06 00:09:07 +00:00
GitLab Bot 78782cd1eb Add latest changes from gitlab-org/gitlab@master 2023-04-06 15:08:20 +00:00
GitLab Bot 61666f277a Add latest changes from gitlab-org/gitlab@master 2022-12-01 21:08:18 +00:00
GitLab Bot c86ec1d072 Add latest changes from gitlab-org/gitlab@master 2022-10-26 15:10:10 +00:00
GitLab Bot eef3d92529 Add latest changes from gitlab-org/gitlab@master 2022-06-08 21:08:52 +00:00
GitLab Bot f4ea1f8998 Add latest changes from gitlab-org/gitlab@master 2022-06-08 09:09:42 +00:00
GitLab Bot c4b4a75c35 Add latest changes from gitlab-org/gitlab@master 2022-02-24 15:15:02 +00:00
GitLab Bot f8975b16d1 Add latest changes from gitlab-org/gitlab@master 2021-07-01 21:08:38 +00:00
GitLab Bot a880341a7b Add latest changes from gitlab-org/gitlab@master 2021-05-25 18:10:42 +00:00
GitLab Bot 06d5641a54 Add latest changes from gitlab-org/gitlab@master 2021-05-10 00:10:37 +00:00
GitLab Bot d5098d9fe3 Add latest changes from gitlab-org/gitlab@master 2020-08-21 15:10:03 +00:00
GitLab Bot c59765a50a Add latest changes from gitlab-org/gitlab@master 2020-06-24 18:09:03 +00:00
GitLab Bot c36e59283e Add latest changes from gitlab-org/gitlab@master 2020-01-30 00:09:09 +00:00
GitLab Bot 2399724614 Add latest changes from gitlab-org/gitlab@master 2020-01-21 03:08:37 +00:00
GitLab Bot a5ab3467a7 Add latest changes from gitlab-org/gitlab@master 2020-01-13 15:07:53 +00:00
GitLab Bot 185f428fa5 Add latest changes from gitlab-org/gitlab@master 2019-10-07 12:06:18 +00:00
GitLab Bot b7dfe2ae40 Add latest changes from gitlab-org/gitlab@master 2019-09-13 13:26:31 +00:00
Thong Kuah f540ffcef6 Add frozen_string_literal to spec/lib (part 1) 
Using the sed script from
https://gitlab.com/gitlab-org/gitlab-ce/issues/59758
 2019-07-26 13:25:07 +12:00
Mario de la Ossa 02741ca4c5
Backport 5480-epic-notifications from EE 2018-05-07 12:58:47 -06:00
Lin Jen-Shin f097e4dbcd Don't send rejection mails for all auto-generated mails 
Also make it easier to have mailer helper
 2017-08-03 00:40:10 +08:00
Rémy Coutable ddccd24c13 Remove superfluous lib: true, type: redis, service: true, models: true, services: true, no_db: true, api: true 
Signed-off-by: Rémy Coutable <remy@rymai.me>
 2017-07-27 14:31:53 +02:00
Sean McGivern eb490365b5 Handle incoming emails from aliases correctly 
These set the 'actual' destination email in one of the Delivered-To lines, so
check those too.
 2017-05-03 20:51:10 +01:00
Sean McGivern 08b1380ff7 Don't blow up when email has no References header 
If an email doesn't match our incoming email patterns on the To header, we fall
back to the References header. If there was no References header, we'd raise an
exception, when we'd be better off acting as if it was empty.
 2017-05-01 14:25:04 +01:00
Lin Jen-Shin 8c0b619d40 Split tests into their own classes 2016-05-24 17:30:36 +08:00
Lin Jen-Shin 1f5d55907a Merge the places where exceptions could be raised 2016-05-24 01:23:07 +08:00
Lin Jen-Shin c2bc15a766 Use the authentication_token for finding the user 2016-05-20 17:38:08 -05:00
Lin Jen-Shin 9436a444f3 Rename reply_key to mail_key 2016-05-20 13:05:57 -05:00
Lin Jen-Shin 4b341dea55 Actually there's no such case 2016-05-20 12:52:53 -05:00
Lin Jen-Shin a7c823a573 Give ProjectNotFound when the project is not readable 2016-05-18 17:57:14 -05:00
Lin Jen-Shin c337e748d3 so we use separate classes to handle different tasks 2016-05-18 17:25:45 -05:00
Lin Jen-Shin 8156475ea5 Report better errors. TODO: Enable skipped test 2016-05-16 21:27:16 +00:00
Lin Jen-Shin a065c8d5d8 Create a new issue via: incoming+group/project+AUTH_TOKEN@... 2016-05-16 21:27:16 +00:00
Lin Jen-Shin 347ee6cc91 Alloy empty reply for new issues, but not response 2016-05-16 21:27:16 +00:00
Lin Jen-Shin 6cfd028278 Implement #3243 New Issue by email 
So we extend Gitlab::Email::Receiver for this new behaviour,
however we might want to split it into another class for better
testing it.

Another issue is that, currently it's using this to parse project
identifier:

    Gitlab::IncomingEmail.key_from_address

Which is using:

    Gitlab.config.incoming_email.address

for the receiver name. This is probably `reply` because it's used
for replying to a specific issue. We might want to introduce another
config for this, or just use `reply` instead of `incoming`.

I'll prefer to introduce a new config for this, or just change
`reply` to `incoming` because it would make sense for replying to
there, too.

The email template used in tests were copied and modified from:
`emails/valid_reply.eml` which I hope is ok.
 2016-05-16 21:27:16 +00:00
Lin Jen-Shin 2375b437bd Fix a typo 2016-05-16 21:27:16 +00:00
Rémy Coutable 9f218fc184 Improve and finish the fallback to the In-Reply-To and References header for the reply-by-email feature 
A few things to note:
- The IncomingEmail feature is now enabled even without a
  correctly-formatted sub-address
- Message-ID for new thread mail are kept the same so that subsequent
  notifications to this thread are grouped in the thread by the email
  service that receives the notification
  (i.e. In-Reply-To of the answer == Message-ID of the first thread message)
- To maximize our chance to be able to retrieve the reply key, we look
  for it in the In-Reply-To header and the References header
- The pattern for the fallback reply message id is "reply-[key]@[gitlab_host]"
- Improve docs thanks to Axil
 2016-03-25 13:05:15 +01:00
David Padilla 31e76baf61 Fix #2364. Fall back to In-Reply-To header when reply key not available 2016-03-25 13:05:15 +01:00
Douwe Maan 1e927d39b4 Update spec 2016-01-07 15:51:12 +01:00
Douwe Maan 13d6bab177 Tag lib specs 2015-12-09 11:55:42 +01:00
Douwe Maan ee028d9d60 Rename reply_by_email to incoming_email to prepare for the future. 2015-09-21 10:35:37 +02:00
Douwe Maan 69708dab9f Block blocked users from replying to threads by email. 2015-08-21 10:14:45 -07:00
Douwe Maan 48e25a019a Add stub_reply_by_email_setting helper. 2015-08-20 13:21:22 -07:00
Douwe Maan 54b04f1c5b Add fixture_file helper. 2015-08-20 12:41:47 -07:00