BigW Consortium Gitlab

  1. 04 Nov, 2016 2 commits
  2. 01 Nov, 2016 2 commits
    • Allow to search for user by secondary email address in the admin interface · f8530580
      Yar authored
      It is not possible to search for a user by his secondary email address in
      the Users search bar in the admin interface(/admin/users). A use-case could
       be that an admin wants to remove a specific secondary email address of an
      user, because it interferes with another user. Issue #23761
      
      This commit adds ability to search not only by main email, but also
      by any secondary email in the admin interface.
    • Rename :name search parameter to :search_query at /admin/users · 6893bccd
      Yar authored
      The parameter is used to search users by several criretia was
      called :name. This request renames it to :search_query which closer
      to it actual perpose
  3. 07 Oct, 2016 1 commit
    • Enable CacheMarkdownField for the remaining models · 99205515
      Nick Thomas authored
      This commit alters views for the following models to use the markdown cache if
      present:
      
      * AbuseReport
      * Appearance
      * ApplicationSetting
      * BroadcastMessage
      * Group
      * Issue
      * Label
      * MergeRequest
      * Milestone
      * Project
      
      At the same time, calls to `escape_once` have been moved into the `single_line`
      Banzai pipeline, so they can't be missed out by accident and the work is done
      at save, rather than render, time.
  4. 28 Sep, 2016 1 commit
  5. 15 Sep, 2016 2 commits
  6. 13 Sep, 2016 2 commits
  7. 31 Aug, 2016 1 commit
  8. 25 Aug, 2016 1 commit
    • Handle unavailable system info · 085e1f89
      Sean McGivern authored
      For Linux with the grsecurity patches applied, paths in `/proc` may not
      be readable, so handle those cases and show a message rather than
      blowing up.
  9. 23 Aug, 2016 1 commit
  10. 19 Aug, 2016 1 commit
    • Support integration with Koding (online IDE) · a927a9bf
      Gokmen Goksel authored
      Koding: #index: landing page for Koding integration
      
      If enabled it will provide a link to open remote Koding instance url
      for now we are also providing the sneak preview video for how
      integration works in detail.
      
      Repository: check whether .koding.yml file exists on repository
      
      Projects: landing page: show Run in IDE (Koding) button if repo has stack file
      
      Projects: MR: show Run in IDE Koding button if repo has stack file on active branch
      
      ProjectHelpers: add_koding_stack: stack generator for provided project
      
      With this helper we will auto-generate the required stack template
      for a given project. For the feature we can request this base template
      from the running Koding instance on integration.
      
      Currently this will provide users to create a t2.nano instance on aws
      and it'll automatically configures the instance for basic requirements.
      
      Projects: empty state and landing page provide shortcuts to create stack
      
      projects_helper: use branch on checkout and provide an entry point
      
      This ${var.koding_queryString_branch} will be replaced with the branch
      provided in query string which will allow us to use same stack template
      for different branches of the same repository.
      
      ref: https://github.com/koding/koding/pull/8597/commits/b8c0e43c4c24bf132670aa8a3cfb0d634acfd09b
      
      projects_helper: provide sha info in query string to use existing vms
      
      With this change we'll be able to query existing vms on Koding side
      based on the commit id that they've created.
      
      ref: https://github.com/koding/koding/pull/8597/commits/1d630fadf31963fa6ccd3bed92e526761a30a343
      
      Integration: Docs: Koding documentation added
      
      Disable /koding route if integration is disabled
      
      Use application settings to enable Koding
      
      Projects_helper: better indentation with strip_heredoc usage
      
      Projects_helper: return koding_url as is if there is no project provided
      
      current_settings: set koding_enabled: false by default
      
      Koding_Controller: to render not_found once integration is disabled
      
      Dashboard_specs: update spec for Koding enabled case
      
      Projects_Helper: make repo dynamic
      
      ref: https://github.com/koding/koding/pull/8597/commits/4d615242f45aaea4c4986be84ecc612b0bb1514c
      
      Updated documentation to have right format
  11. 18 Aug, 2016 1 commit
  12. 15 Aug, 2016 4 commits
  13. 11 Aug, 2016 1 commit
    • Fix bug where destroying a namespace would not always destroy projects · cb8a425b
      Stan Hu authored
      There is a race condition in DestroyGroupService now that projects are deleted asynchronously:
      
      1. User attempts to delete group
      2. DestroyGroupService iterates through all projects and schedules a Sidekiq job to delete each Project
      3. DestroyGroupService destroys the Group, leaving all its projects without a namespace
      4. Projects::DestroyService runs later but the can?(current_user,
         :remove_project) is `false` because the user no longer has permission to
         destroy projects with no namespace.
      5. This leaves the project in pending_delete state with no namespace/group.
      
      Projects without a namespace or group also adds another problem: it's not possible to destroy the container
      registry tags, since container_registry_path_with_namespace is the wrong value.
      
      The fix is to destroy the group asynchronously and to run execute directly on Projects::DestroyService.
      
      Closes #17893
  14. 26 Jul, 2016 1 commit
  15. 20 Jul, 2016 2 commits
  16. 19 Jul, 2016 3 commits
  17. 18 Jul, 2016 6 commits
  18. 08 Jul, 2016 1 commit
  19. 07 Jul, 2016 3 commits
  20. 05 Jul, 2016 2 commits
  21. 01 Jul, 2016 2 commits