1. 11 Feb, 2019 1 commit
  2. 23 Jan, 2019 1 commit
  3. 11 Jan, 2019 1 commit
  4. 20 Nov, 2018 1 commit
  5. 15 Nov, 2018 1 commit
  6. 14 Nov, 2018 1 commit
  7. 13 Oct, 2018 2 commits
  8. 04 Oct, 2018 1 commit
    • Tomasz Maczukin's avatar
      Simplify runner registration token resetting · 42af2295
      Tomasz Maczukin authored
      This icommit adds several changes related to the same topic
      - resetting a Runner registration token:
      
      1. On Project settings page it adds a button for resetting the
         registration token and it removes the Runner token field
         that was confusing all GitLab users.
      
      2. On Group settings page it adds the same button for resetting
         the registration token.
      
      3. On Admin Runners settings page it moves the button to the same
         place as in Project and Group settings and it changes slightly
         the page layout to make it more similar to Group and Project
         setting pages.
      
      4. It refactorizes a little the partial that prints runner
         registration description. Thanks to this Project, Group
         and Admin settings of the Runner are re-using the same
         code to generate the button.
      
      5. Updates the translations of changed text.
      42af2295
  9. 02 Oct, 2018 1 commit
  10. 19 Sep, 2018 1 commit
  11. 05 Sep, 2018 1 commit
  12. 01 Aug, 2018 1 commit
  13. 04 Jul, 2018 1 commit
  14. 01 Jul, 2018 2 commits
  15. 29 Jun, 2018 1 commit
  16. 21 Jun, 2018 1 commit
  17. 15 Jun, 2018 1 commit
  18. 13 Jun, 2018 2 commits
  19. 11 Jun, 2018 2 commits
  20. 08 Jun, 2018 2 commits
    • Bob Van Landuyt's avatar
      Users can accept terms during registration · 3d713ac1
      Bob Van Landuyt authored
      When a user checks the `accept` checkbox, we will track that
      acceptance as usual. That way they don't need to accept again after
      they complete the registration.
      
      When an unauthenticated user visits the `/-/users/terms` page, there
      is no button to accept, decline or continue. The 'current-user menu'
      is also hidden from the top bar.
      3d713ac1
    • Andreas Kämmerle's avatar
      Update settings section titles · 6a077c54
      Andreas Kämmerle authored
      6a077c54
  21. 07 Jun, 2018 1 commit
  22. 06 Jun, 2018 3 commits
  23. 01 Jun, 2018 1 commit
  24. 31 May, 2018 1 commit
  25. 29 May, 2018 1 commit
  26. 28 May, 2018 1 commit
  27. 21 May, 2018 2 commits
  28. 16 May, 2018 2 commits
  29. 15 May, 2018 1 commit
  30. 09 May, 2018 1 commit
  31. 04 May, 2018 1 commit
    • Bob Van Landuyt's avatar
      Enforces terms in the web application · 7684217d
      Bob Van Landuyt authored
      This enforces the terms in the web application. These cases are
      specced:
      
      - Logging in: When terms are enforced, and a user logs in that has not
        accepted the terms, they are presented with the screen. They get
        directed to their customized root path afterwards.
      - Signing up: After signing up, the first screen the user is presented
        with the screen to accept the terms. After they accept they are
        directed to the dashboard.
      - While a session is active:
        - For a GET: The user will be directed to the terms page first,
          after they accept the terms, they will be directed to the page
          they were going to
        - For any other request: They are directed to the terms, after they
          accept the terms, they are directed back to the page they came
          from to retry the request. Any information entered would be
          persisted in localstorage and available on the page.
      7684217d