- 04 May, 2017 1 commit
-
-
Valery Sizov authored
-
- 01 May, 2017 1 commit
-
-
Robert Speicher authored
-
- 26 Apr, 2017 1 commit
-
-
Sean McGivern authored
- Ignore JS fixtures - Ignore qa directory - Rewrite concern specs to put concern name first
-
- 06 Apr, 2017 1 commit
-
-
Toon Claes authored
Visit `/rails/mailers/notify` on your local running GitLab instance to show a preview pipeline success emails.
-
- 05 Apr, 2017 5 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
- 03 Apr, 2017 1 commit
-
-
Rémy Coutable authored
FFaker can generate data that randomly break our test suite. This simplifies our factories and use sequences which are more predictive. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 27 Mar, 2017 1 commit
-
-
Robert Speicher authored
-
- 21 Mar, 2017 2 commits
-
-
Robert Speicher authored
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.
-
Robert Speicher authored
This shared example was only used by this spec so having it in a separate file provided no benefit, at the cost of clarity. This also reduces the three `it` blocks into a single test with `aggregate_failures`.
-
- 17 Mar, 2017 2 commits
-
-
Kamil Trzciński authored
-
Rémy Coutable authored
This solves transient failures when a text contains HTML-escapable characters such as `'`. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 14 Mar, 2017 1 commit
-
-
Nick Thomas authored
-
- 23 Feb, 2017 2 commits
-
-
Douwe Maan authored
This reverts commit cb10b725c8929b8b4460f89c9d96c773af39ba6b.
-
Douwe Maan authored
-
- 28 Nov, 2016 3 commits
-
-
Ruben Davila authored
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 authored
-
Sean McGivern authored
-
- 25 Nov, 2016 5 commits
-
-
hhoopes authored
-
hhoopes authored
* 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 authored
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 authored
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 authored
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).
-
- 18 Nov, 2016 1 commit
-
-
Lin Jen-Shin authored
This would fix long standing failures running tests on my development machine, which set `Gitlab.config.gitlab.host` to another host because it's not my local computer. Now I finally cannot withstand it and decided to fix them once and for all.
-
- 11 Nov, 2016 1 commit
-
-
Nick Thomas authored
-
- 22 Oct, 2016 1 commit
-
-
Jared Ready authored
-
- 17 Oct, 2016 1 commit
-
-
Lin Jen-Shin authored
-
- 11 Oct, 2016 1 commit
-
-
tiagonbotelho authored
-
- 03 Oct, 2016 7 commits
- 28 Sep, 2016 1 commit
-
-
Rémy Coutable authored
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: Rémy Coutable <remy@rymai.me>
-
- 26 Sep, 2016 1 commit
-
-
Sean McGivern authored
-