1. 07 Nov, 2018 1 commit
    • Tiago Botelho's avatar
      User can keep their commit email private · c239452b
      Tiago Botelho authored
      The private commit email is automatically generated in the format:
      GitLab instance admins are able to change the HOSTNAME portion,
      that defaults to Gitlab's hostname, to whatever they prefer.
  2. 05 Nov, 2018 1 commit
  3. 10 Oct, 2018 1 commit
    • Zeger-Jan van de Weg's avatar
      Remove Git circuit breaker · 30b4ce94
      Zeger-Jan van de Weg authored
      Was introduced in the time that GitLab still used NFS, which is not
      required anymore in most cases. By removing this, the API it calls will
      return empty responses. This interface has to be removed in the next
      major release, expected to be 12.0.
  4. 01 Oct, 2018 1 commit
    • Oswaldo Ferreira's avatar
      Make single diff patch limit configurable · 4fbca2a3
      Oswaldo Ferreira authored
      - Creates a new column to hold the single patch limit value on
      - Allows updating this value through the application_settings API
      - Calculates single diff patch collapsing limit based on
      diff_max_patch_bytes column
      - Updates diff limit documentation
      - Adds documentation (with warning) as of how one can update this limit
  5. 12 Sep, 2018 1 commit
  6. 30 Aug, 2018 1 commit
  7. 26 Jun, 2018 1 commit
  8. 04 Jun, 2018 1 commit
  9. 31 May, 2018 1 commit
  10. 30 May, 2018 1 commit
  11. 29 May, 2018 1 commit
  12. 23 May, 2018 1 commit
  13. 04 May, 2018 1 commit
    • Bob Van Landuyt's avatar
      Store application wide terms · 3d6d0a09
      Bob Van Landuyt authored
      This allows admins to define terms in the application settings.
      Every time the terms are adjusted, a new version is stored and becomes
      the 'active' version. This allows tracking which specific version was
      accepted by a user.
  14. 22 Jan, 2018 2 commits
  15. 08 Dec, 2017 1 commit
    • Bob Van Landuyt's avatar
      Move the circuitbreaker check out in a separate process · f1ae1e39
      Bob Van Landuyt authored
      Moving the check out of the general requests, makes sure we don't have
      any slowdown in the regular requests.
      To keep the process performing this checks small, the check is still
      performed inside a unicorn. But that is called from a process running
      on the same server.
      Because the checks are now done outside normal request, we can have a
      simpler failure strategy:
      The check is now performed in the background every
      `circuitbreaker_check_interval`. Failures are logged in redis. The
      failures are reset when the check succeeds. Per check we will try
      `circuitbreaker_access_retries` times within
      `circuitbreaker_storage_timeout` seconds.
      When the number of failures exceeds
      `circuitbreaker_failure_count_threshold`, we will block access to the
      After `failure_reset_time` of no checks, we will clear the stored
      failures. This could happen when the process that performs the checks
      is not running.
  16. 29 Nov, 2017 1 commit
  17. 23 Nov, 2017 1 commit
  18. 23 Oct, 2017 1 commit
  19. 21 Oct, 2017 1 commit
  20. 19 Oct, 2017 1 commit
  21. 17 Oct, 2017 1 commit
  22. 16 Oct, 2017 1 commit
  23. 11 Sep, 2017 1 commit
  24. 31 Aug, 2017 1 commit
    • Zeger-Jan van de Weg's avatar
      Implement the implied CI/CD config for AutoDevOps · 6ed49040
      Zeger-Jan van de Weg authored
      Behind an application setting, which defaults to false, this commit
      implements the implied CI/CD config. Which means that in the case we
      can't find the `.gitlab-ci.yml` on the commit we want to start a
      pipeline for, we fall back to an implied configuration.
      For now the Bash template has been copied to
      `Auto-Devops.gitlab-ci.yml` so the tests actually work.
      Fixes #34777
  25. 30 Aug, 2017 4 commits
    • Nick Thomas's avatar
      More review comments · 29b40db5
      Nick Thomas authored
    • Nick Thomas's avatar
    • Nick Thomas's avatar
      Rework the permissions model for SSH key restrictions · 68470602
      Nick Thomas authored
      `allowed_key_types` is removed and the `minimum_<type>_bits` fields are
      renamed to `<tech>_key_restriction`. A special sentinel value (`-1`) signifies
      that the key type is disabled.
      This also feeds through to the UI - checkboxes per key type are out, inline
      selection of "forbidden" and "allowed" (i.e., no restrictions) are in.
      As with the previous model, unknown key types are disallowed, even if the
      underlying ssh daemon happens to support them. The defaults have also been
      changed from the lowest known bit size to "no restriction". So if someone
      does happen to have a 768-bit RSA key, it will continue to work on upgrade, at
      least until the administrator restricts them.
    • Nick Thomas's avatar
      Add settings for minimum key strength and allowed key type · b0f982fb
      Nick Thomas authored
      This is an amalgamation of:
      * Cory Hinshaw: Initial implementation !5552
      * Rémy Coutable: Updates !9350
      * Nick Thomas: Resolve conflicts and add ED25519 support !13712
  26. 27 Jul, 2017 2 commits
  27. 10 Jul, 2017 1 commit
  28. 07 Jul, 2017 1 commit
  29. 06 Jul, 2017 1 commit
  30. 14 Jun, 2017 1 commit
  31. 11 May, 2017 1 commit
    • Sean McGivern's avatar
      Allow disabling usage ping in `gitlab.yml` · 3c546acf
      Sean McGivern authored
      Setting `usage_ping_enabled` to false in `gitlab.yml`:
      1. Disables the usage ping, regardless of the value stored in the database.
      2. Prevents the usage ping from being enabled through the admin panel. It can
         only be enabled by either removing the line from `gitlab.yml` and configuring
         through the admin panel, or setting it to true in `gitlab.yml`.
  32. 10 May, 2017 1 commit
  33. 26 Apr, 2017 1 commit
  34. 23 Feb, 2017 2 commits
    • Douwe Maan's avatar
      Revert "Enable Style/DotPosition" · 56de781a
      Douwe Maan authored
      This reverts commit e00fb2bdc2090e9cabeb1eb35a2672a882cc96e9.
      # Conflicts:
      #	.rubocop.yml
      #	.rubocop_todo.yml
      #	lib/gitlab/ci/config/entry/global.rb
      #	lib/gitlab/ci/config/entry/jobs.rb
      #	spec/lib/gitlab/ci/config/entry/factory_spec.rb
      #	spec/lib/gitlab/ci/config/entry/global_spec.rb
      #	spec/lib/gitlab/ci/config/entry/job_spec.rb
      #	spec/lib/gitlab/ci/status/build/factory_spec.rb
      #	spec/lib/gitlab/incoming_email_spec.rb
    • Douwe Maan's avatar
      Revert "Prefer leading style for Style/DotPosition" · 1fe7501b
      Douwe Maan authored
      This reverts commit cb10b725c8929b8b4460f89c9d96c773af39ba6b.