- 25 5月, 2017 1 次提交
-
-
由 Ruben Davila 提交于
There was a race condition issue when the application was generating an email and was using a language that was previously being used in other request.
-
- 04 5月, 2017 1 次提交
-
-
由 Valery Sizov 提交于
-
- 01 5月, 2017 1 次提交
-
-
由 Robert Speicher 提交于
-
- 06 4月, 2017 4 次提交
-
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
- 04 4月, 2017 1 次提交
-
-
由 Rémy Coutable 提交于
FFaker can generate data that randomly break our test suite. This simplifies our factories and use sequences which are more predictive. Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 28 3月, 2017 1 次提交
-
-
由 Robert Speicher 提交于
-
- 22 3月, 2017 1 次提交
-
-
由 Robert Speicher 提交于
We perform a bunch of setup for most of these cases, and it didn't make sense to do an entirely new costly setup just to test a different string in the same body of the email we just generated in the last test.
-
- 17 3月, 2017 1 次提交
-
-
由 Rémy Coutable 提交于
This solves transient failures when a text contains HTML-escapable characters such as `'`. Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 14 3月, 2017 1 次提交
-
-
由 Nick Thomas 提交于
-
- 29 11月, 2016 3 次提交
-
-
由 Ruben Davila 提交于
This new global setting will allow admins to specify if HTML emails should be sent or not, this is basically useful when system administrators want to save some disk space by avoiding emails in HTML format and using only the Plain Text version.
-
由 Sean McGivern 提交于
-
由 Sean McGivern 提交于
-
- 25 11月, 2016 5 次提交
-
-
由 hhoopes 提交于
-
由 hhoopes 提交于
* Added keyword arguments to truncated_diff_lines method to allow for using highlighting or not (html templates vs. text) * Tweaked templates for consistency and format appropriateness
-
由 hhoopes 提交于
Previously the `truncated_diff_lines` method for outputting a discussion diff took in already highlighted lines, which meant it wasn't reuseable for truncating ANY lines. In the way it was used, it also meant that for any email truncation, the whole diff was being highlighted before being truncated, meaning wasted time highlighting lines that wouldn't even be used (granted, they were being memoized, so perhaps this wasn't that great of an issue). I refactored truncation away from highlighting, in order to truncate formatted diffs for text templates in email, using `>`s to designate each line, but otherwise retaining the parsing already done to create `diff_lines`. Additionally, while notes on merge requests or commits had already been tested, there was no existing test for notes on a diff on an MR or commit. Added mailer tests for such, and a unit test for truncating diff lines.
-
由 hhoopes 提交于
Currently comments on commits and merge requests do not require merge request- or commit-specific information, but can use the same template. Rather than change the method which calls the template, I opted to keep the templates separate and create a new template to highlight their identicality, while preserving the option to distinguish them from each other in the future. Also removed some of the inconsistencies between text and html email versions. Still needed is a text-only version of git diffs and testing.
-
由 hhoopes 提交于
Added diff hunks to notification emails of messages on merge requests. This provides code context to the note. Uses existing template for formatting a diff for email (from repository push notifications).
-
- 11 11月, 2016 1 次提交
-
-
由 Nick Thomas 提交于
-
- 23 10月, 2016 1 次提交
-
-
由 Jared Ready 提交于
-
- 11 10月, 2016 1 次提交
-
-
由 tiagonbotelho 提交于
-
- 03 10月, 2016 5 次提交
- 28 9月, 2016 1 次提交
-
-
由 Rémy Coutable 提交于
Changes include: - Ensure Member.add_user is not called directly when not necessary - New GroupMember.add_users_to_group to have the same abstraction level as for Project - Refactor Member.add_user to take a source instead of an array of members - Fix Rubocop offenses - Always use Project#add_user instead of project.team.add_user - Factorize users addition as members in Member.add_users_to_source - Make access_level a keyword argument in GroupMember.add_users_to_group and ProjectMember.add_users_to_projects - Destroy any requester before adding them as a member - Improve the way we handle access requesters in Member.add_user Instead of removing the requester and creating a new member, we now simply accepts their access request. This way, they will receive a "access request granted" email. - Fix error that was previously silently ignored - Stop raising when access level is invalid in Member, let Rails validation do their work Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 22 9月, 2016 1 次提交
-
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 20 9月, 2016 1 次提交
-
-
由 Maximiliano Perez Coto 提交于
* Created a force=true param that will continue with the previous behaviour of the unsubscribe method * Created a filter for not-logged users so they see a unsubsribe confirmation page * Added the List-Unsubscribe header on emails so the email client can display it on top
-
- 09 8月, 2016 1 次提交
-
-
由 tiagonbotelho 提交于
-
- 03 8月, 2016 2 次提交
-
-
由 Paco Guzman 提交于
This object will manage Gitlab::Git::Compare instances
-
由 Adam Niedzielski 提交于
-
- 22 7月, 2016 1 次提交
-
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 07 7月, 2016 1 次提交
-
-
由 Douwe Maan 提交于
-
- 02 7月, 2016 1 次提交
-
-
由 Grzegorz Bizon 提交于
-
- 01 7月, 2016 1 次提交
-
-
由 Rémy Coutable 提交于
And create new Project#requesters, Group#requesters scopes. Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 20 6月, 2016 1 次提交
-
-
由 Rémy Coutable 提交于
A project in a group can have no explicit owners/masters, in that case we fallbacks to the group's owners/masters. Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 16 6月, 2016 1 次提交
-
-
由 James Lopez 提交于
This reverts commit 13e37a3e.
-