Read about our upcoming Code of Conduct on this issue

  1. 12 Jul, 2019 1 commit
  2. 11 Jul, 2019 1 commit
  3. 10 Jul, 2019 1 commit
  4. 09 Jul, 2019 1 commit
    • Markus Koller's avatar
      Centralize config for markdownlint · a1668bf8a707
      Markus Koller authored
      The configuration is currently only specified in CI, by moving it into
      `.mdlrc` we get immediate feedback locally in supported editors.
      
      To ensure `mdl` is available it's also added to the `Gemfile`, though
      CI will still use the version installed in the `gitlab-docs-lint` image.
      a1668bf8a707
  5. 08 Jul, 2019 1 commit
  6. 06 Jul, 2019 2 commits
  7. 05 Jul, 2019 1 commit
  8. 04 Jul, 2019 1 commit
  9. 01 Jul, 2019 1 commit
  10. 28 Jun, 2019 2 commits
  11. 24 Jun, 2019 1 commit
  12. 17 Jun, 2019 1 commit
  13. 16 Jun, 2019 1 commit
  14. 14 Jun, 2019 1 commit
  15. 12 Jun, 2019 1 commit
    • Heinrich Lee Yu's avatar
      Upgrade to Capybara 3 · b551b393a017
      Heinrich Lee Yu authored
      Fix whitespace in specs because normalize_ws is slightly
      different from Capybara 2 behavior
      b551b393a017
  16. 08 Jun, 2019 1 commit
  17. 07 Jun, 2019 1 commit
  18. 06 Jun, 2019 1 commit
  19. 05 Jun, 2019 1 commit
  20. 03 Jun, 2019 1 commit
    • Toon Claes's avatar
      Add activerecord-explain-analyze gem · 94a7bd2a33cb
      Toon Claes authored
      This gem allows you to get the `EXPLAIN ANALYZE` query plan, directly
      from the Rails console.
      
      The gem is installed with `require: false`, but if it was loaded on
      launch, this would be it's memory load:
      
      ```
      TOP: 145.3086 MiB
        rails/all: 22.4844 MiB
        ...
        activerecord-explain-analyze: 2.9648 MiB
          active_record/connection_adapters/postgresql_adapter: 2.9648 MiB
            pg: 2.9648 MiB
              pg_ext: 2.9648 MiB
        ...
      ```
      94a7bd2a33cb
  21. 29 May, 2019 1 commit
    • Jan Provaznik's avatar
      Added rack-timeout for Puma · 84552e43b440
      Jan Provaznik authored
      It assures that requests are aborted after 60 seconds, otherwise
      an exception is raised. This exception is logged by Sentry, also
      there is a Prometheus counter for measuring number of requests in each
      state.
      84552e43b440
  22. 27 May, 2019 1 commit
  23. 24 May, 2019 1 commit
  24. 22 May, 2019 3 commits
  25. 21 May, 2019 1 commit
  26. 20 May, 2019 2 commits
  27. 16 May, 2019 3 commits
  28. 07 May, 2019 2 commits
  29. 06 May, 2019 1 commit
  30. 05 May, 2019 2 commits
  31. 02 May, 2019 1 commit
    • Luke Duncalfe's avatar
      Add support for two-step Gitaly Rebase RPC · d319cb340511
      Luke Duncalfe authored
      The new two-step Gitaly `Rebase` RPC yields the rebase commit SHA to the
      client before proceeding with the rebase.
      
      This avoids an issue where the rebase commit SHA was returned when the
      RPC had fully completed, and in some cases this would be after the Rails
      `post_receive` worker services had already run. In these situations,
      the merge request did not yet have its rebase_commit_sha attribute set
      introducing the possibility for bugs (such as previous approvals being
      reset).
      
      https://gitlab.com/gitlab-org/gitlab-ee/issues/5966
      d319cb340511