GitLab steht wegen Wartungsarbeiten am Montag, den 10. Mai, zwischen 17:00 und 19:00 Uhr nicht zur Verfügung.

  1. 11 Aug, 2017 1 commit
  2. 02 Aug, 2017 1 commit
  3. 05 Jul, 2017 1 commit
  4. 14 Jun, 2017 1 commit
  5. 25 May, 2017 1 commit
  6. 04 May, 2017 1 commit
  7. 01 May, 2017 1 commit
  8. 05 Apr, 2017 4 commits
  9. 03 Apr, 2017 1 commit
  10. 28 Mar, 2017 1 commit
  11. 22 Mar, 2017 1 commit
    • Robert Speicher's avatar
      Combine redundant `it` blocks in Notify spec · a6e43aa2
      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.
      a6e43aa2
  12. 17 Mar, 2017 1 commit
  13. 14 Mar, 2017 1 commit
  14. 28 Nov, 2016 3 commits
  15. 25 Nov, 2016 5 commits
    • hhoopes's avatar
      Clean up rubocop complaint · c0931722
      hhoopes authored
      c0931722
    • hhoopes's avatar
      Add keyword arguments to truncated_diff method · a761c59a
      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
      a761c59a
    • hhoopes's avatar
      Change diff highlight/truncate for reusability · f928dba9
      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.
      f928dba9
    • hhoopes's avatar
      Add new template to handle both commit & mr notes · 24070bac
      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.
      24070bac
    • hhoopes's avatar
      Add diff hunks to notification emails on MR · 38ed96e9
      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).
      38ed96e9
  16. 11 Nov, 2016 1 commit
  17. 23 Oct, 2016 1 commit
  18. 11 Oct, 2016 1 commit
  19. 03 Oct, 2016 5 commits
  20. 28 Sep, 2016 1 commit
    • Rémy Coutable's avatar
      Allow Member.add_user to handle access requesters · ec0061a9
      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: default avatarRémy Coutable <remy@rymai.me>
      ec0061a9
  21. 22 Sep, 2016 1 commit
  22. 20 Sep, 2016 1 commit
  23. 09 Aug, 2016 1 commit
  24. 03 Aug, 2016 1 commit
  25. 02 Aug, 2016 1 commit
  26. 22 Jul, 2016 1 commit
  27. 07 Jul, 2016 1 commit