1. 01 May, 2017 1 commit
  2. 27 Apr, 2017 1 commit
  3. 18 Apr, 2017 1 commit
  4. 14 Apr, 2017 1 commit
  5. 04 Apr, 2017 1 commit
  6. 03 Apr, 2017 2 commits
  7. 31 Mar, 2017 1 commit
  8. 28 Mar, 2017 1 commit
  9. 25 Mar, 2017 1 commit
  10. 24 Mar, 2017 1 commit
  11. 23 Mar, 2017 2 commits
  12. 21 Mar, 2017 1 commit
  13. 06 Mar, 2017 2 commits
    • Robert Speicher's avatar
      Fix Projects::UploadService spec · 2cfb67df
      Robert Speicher authored
      For reasons unknown, this spec was passing a project's repository as the
      first argument to `Projects::UploadService`, while it was expecting the
      project itself.
      
      Previously this wasn't a problem because `FileUploader` only needed the
      object to respond to `path_with_namespace`, which Repository and Project
      both did. But now because of `Upload` and its polymorphic association,
      it expects the object to respond to `primary_key`.
      2cfb67df
    • Grzegorz Bizon's avatar
      8f227f23
  14. 05 Mar, 2017 1 commit
  15. 23 Feb, 2017 3 commits
  16. 22 Feb, 2017 1 commit
  17. 19 Feb, 2017 1 commit
    • Stan Hu's avatar
      Prevent project team from being truncated too early during project destruction · 45f94ea7
      Stan Hu authored
      There are two issues with truncating the project team early:
      
      1. `Projects::UnlinkForkService` may not close merge requests properly since
         permissions may be revoked early.
      
      2. If an error is encountered during flushing of caches, then the user will
         lose all privileges, possibly causing an issue on deletion on retry.
      45f94ea7
  18. 07 Feb, 2017 1 commit
    • Yorick Peterse's avatar
      Refresh authorizations when transferring projects · ebae3839
      Yorick Peterse authored
      This ensures that project authorizations are refreshed when moving a
      project from one namespace to another. When doing so the permissions for
      all users of both the old and new namespaces are refreshed.
      
      See #26194 for more information.
      ebae3839
  19. 05 Feb, 2017 1 commit
  20. 03 Feb, 2017 2 commits
  21. 02 Feb, 2017 1 commit
    • Stan Hu's avatar
      Fix GitLab Pages not refreshing upon new content · 23974334
      Stan Hu authored
      Due to autoloading and Ruby scoping, the .update file was never being
      updated due to this error:
      
      ```
      NoMethodError: undefined method `pages' for Projects::Settings:Module
              from /opt/gitlab/embedded/service/gitlab-rails/app/services/projects/update_pages_configuration_service.rb:50:in `pages_update_file'
              from /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/metrics/instrumentation.rb:157:in `pages_update_file'
              from (irb):6
              from /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/railties-4.2.7.1/lib/rails/commands/console.rb:110:in `start'
              from /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/railties-4.2.7.1/lib/rails/commands/console.rb:9:in `start'
              from /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/railties-4.2.7.1/lib/rails/commands/commands_tasks.rb:68:in `console'
              from /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/railties-4.2.7.1/lib/rails/commands/commands_tasks.rb:39:in `run_command!'
              from /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/railties-4.2.7.1/lib/rails/commands.rb:17:in `<top (required)>'
              from bin/rails:9:in `require'
      ```
      
      This error was caught and discarded quietly. This fix exercises this code and fixes the scope problem.
      
      Closes gitlab-com/infrastructure#1058
      23974334
  22. 01 Feb, 2017 2 commits
  23. 31 Jan, 2017 6 commits
  24. 16 Jan, 2017 1 commit
  25. 05 Jan, 2017 1 commit
  26. 03 Jan, 2017 1 commit
  27. 01 Dec, 2016 1 commit
    • Lin Jen-Shin's avatar
      Make deleting with optimistic locking respect NULL · 5747b0d3
      Lin Jen-Shin authored
      For now deleting with optimistic locking is broken when
      lock_version is still NULL, because Rails would try to
      delete with `lock_version = 0` while in the database
      the column is still `NULL`.
      
      The monkey patches would force Rails just pass whatever
      in the column, and stop Rails from casting `NULL` into `0`
      when the value is read from database.
      
      Closes #24766
      5747b0d3
  28. 22 Nov, 2016 1 commit