1. 17 10月, 2018 1 次提交
  2. 15 10月, 2018 1 次提交
  3. 13 10月, 2018 1 次提交
  4. 12 10月, 2018 1 次提交
  5. 10 10月, 2018 1 次提交
    • Z
      Remove Git circuit breaker · 30b4ce94
      Zeger-Jan van de Weg 提交于
      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.
      30b4ce94
  6. 06 10月, 2018 2 次提交
    • G
      Add button to insert table in markdown editor · e9f7908f
      George Tsiolis 提交于
      e9f7908f
    • A
      Add timed incremental rollout to Auto DevOps · 94fc0619
      Alessio Caiazza 提交于
      Auto DevOps deployment strategies now supports timed incremental
      rollout. We are deprecating the usage of INCREMENTAL_ROLLOUT_ENABLED
      environment variable in Auto DevOps template.
      
      The new behavior will be driven by the INCREMENTAL_ROLLOUT_MODE variable
      that can either be manual (same as INCREMENTAL_ROLLOUT_ENABLED) or
      timed.
      
      Rollout deployments will be executed using a 5 minute delay between each
      job.
      94fc0619
  7. 04 10月, 2018 4 次提交
  8. 03 10月, 2018 4 次提交
  9. 02 10月, 2018 2 次提交
  10. 01 10月, 2018 1 次提交
    • O
      Make single diff patch limit configurable · 4fbca2a3
      Oswaldo Ferreira 提交于
      - Creates a new column to hold the single patch limit value on
      application_settings
      - 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
      4fbca2a3
  11. 27 9月, 2018 1 次提交
  12. 26 9月, 2018 1 次提交
  13. 25 9月, 2018 2 次提交
  14. 24 9月, 2018 1 次提交
  15. 22 9月, 2018 1 次提交
  16. 21 9月, 2018 2 次提交
  17. 19 9月, 2018 2 次提交
  18. 12 9月, 2018 1 次提交
  19. 08 9月, 2018 2 次提交
    • M
      03ab130e
    • S
      Delete a container registry asynchronously · 5830d114
      Stan Hu 提交于
      When a container registry has many tags, it's easy for the DELETE call to take more
      than 60 seconds and fail. This can also leave the registry in a bad state with
      null bytes since some of the images have been deleted with tags still pointing to them.
      In addition, we have to prevent users from accidentally initiating the delete multiple
      times or this could leave the registry with orphaned tags.
      
      This commit also adds a flash message to notify the user the registry is scheduled
      for deletion.
      
      Closes #49926, #51063
      5830d114
  20. 07 9月, 2018 9 次提交