Read about our upcoming Code of Conduct on this issue

  1. 06 May, 2019 2 commits
    • Ezekiel Kigbo's avatar
      Added blank lines to meet style guide · 5c1437e23f6e
      Ezekiel Kigbo authored
      Un-nest title variable output
      Update spec test names
      Rename sort_value_most_stars -> sort_value_stars_desc
      Rename sorted_by_stars -> sorted_by_stars_desc
      Renname sort_value_most_stars_asc -> sort_value_stars_asc
      Invert feature check, assign feature condition to a variable
      Inline conditional nav bar rendering
      Invert conditional label
      Added follow up task
      Fix filters returning 0 projects show the wrong view
      Move click action out of test expectation
      Use proper variable name for project in before block
      Rename projects_sort_admin_options_hash
      Renamed projects_sort_admin_options_has to
      old_projects_sort_options_hash as its not only used
      on the admin screen
      Fix extra whitespace errors
      Stub project_list_filter_bar in the projects_helper specs
      Added follow up task for `show_projects?`
      Removed url test expectations
    • Ezekiel Kigbo's avatar
      Update project list specs · f190400ce167
      Ezekiel Kigbo authored
      Add tests to ensure search only executes with a button click or enter,
      sort by Name, Last updated, Created date and Stars and tests for
      Visibility filter
  2. 19 Feb, 2019 1 commit
  3. 31 Jan, 2019 1 commit
    • Steve Azzopardi's avatar
      Stop showing ci for guest users · 1f5c1426bd22
      Steve Azzopardi authored
      When a user is a guest user, and the "Public Pipeline" is set to false
      inside of "Settings > CI/CD > General" the commit status in the project
      dashboard should not be shown.
  4. 23 Jan, 2019 1 commit
    • Steve Azzopardi's avatar
      Stop showing ci for guest users · 2efce6ee7180
      Steve Azzopardi authored
      When a user is a guest user, and the "Public Pipeline" is set to false
      inside of "Settings > CI/CD > General" the commit status in the project
      dashboard should not be shown.
  5. 15 Jan, 2019 1 commit
  6. 07 Nov, 2018 1 commit
  7. 26 Oct, 2018 1 commit
  8. 21 Sep, 2018 1 commit
  9. 09 Jul, 2018 1 commit
  10. 06 Jul, 2018 1 commit
  11. 05 Jul, 2018 1 commit
  12. 31 May, 2018 1 commit
  13. 11 Apr, 2018 1 commit
  14. 06 Mar, 2018 1 commit
    • Stan Hu's avatar
      Fix project dashboard showing the wrong timestamps · fc074650e418
      Stan Hu authored
      Use the max of the `last_activity_at` and `last_repository_updated_at`
      columns. The latter is updated only when a push happens, but the former is
      updated whenever any activity (e.g. issue creation) happens.
      Closes #27181
  15. 22 Dec, 2017 1 commit
  16. 07 Oct, 2017 1 commit
    • Jacopo's avatar
      Replaces `tag: true` into `:tag` in the specs · f4ef7328afe4
      Jacopo authored
      Replaces all the explicit include metadata syntax in the specs (tag:
      true) into the implicit one (:tag).
      Added a cop to prevent future errors and handle autocorrection.
  17. 22 Sep, 2017 1 commit
    • Phil Hughes's avatar
      Add context tabs to dashboard/projects · eb31b7e4abea
      Phil Hughes authored
      This allows users to quickly switch between all projects they have
      access to & there own namespace projects. These tabs also keep
      the same filtering/search options selected so the user can quickly
      switch between the two different contexts.
      Closes #29045
  18. 07 Sep, 2017 1 commit
    • Yorick Peterse's avatar
      Rework how recent push events are retrieved · 9ec66da20412
      Yorick Peterse authored
      Whenever you push to a branch GitLab will show a button to create a
      merge request (should one not exist already). The underlying code to
      display this data was quite inefficient. For example, it involved
      multiple slow queries just to figure out what the most recent push event
      This commit changes the way this data is retrieved so it's much faster.
      This is achieved by caching the ID of the last push event on every push,
      which is then retrieved when loading certain pages. Database queries are
      only executed if necessary and the cached data is removed automatically
      once a merge request has been created, or 2 hours after being stored.
      A trade-off of this approach is that we _only_ track the last event.
      Previously if you were to push to branch A and B then create a merge
      request for branch B we'd still show the widget for branch A. As of this
      commit this is no longer the case, instead we will only show the widget
      for the branch you pushed to most recently. Once a merge request exists
      the widget is no longer displayed. Alternative solutions are either too
      complex and/or too slow, hence the decision was made to settle for this
      Performance Impact
      In the best case scenario (= a user didn't push anything for more than 2
      hours) we perform a single Redis GET per page. Should there be cached
      data we will run a single (and lightweight) SQL query to get the
      event data from the database. If a merge request already exists we will
      run an additional DEL to remove the cache key.
      The difference in response timings can vary a bit per project. On the 99th percentile of time spent in User#recent_push hovers
      between 100 milliseconds and 1 second, while the mean hovers around 50
      milliseconds. With the changes in this MR the expected time spent in
      User#recent_push is expected to be reduced down to just a few
  19. 06 Sep, 2017 1 commit
    • Yorick Peterse's avatar
      Finish migration to the new events setup · 6f43f86cfef6
      Yorick Peterse authored
      This finishes the procedure for migrating events from the old format
      into the new format. Code no longer uses the old setup and the database
      tables used during the migration process are swapped, with the old table
      being dropped.
      While the database migration can be reversed this will 1) take a lot of
      time as data has to be coped around 2) won't restore data in the
      "" column as we have no way of restoring this.
  20. 05 Sep, 2017 1 commit
  21. 02 Aug, 2017 1 commit
  22. 01 Aug, 2017 1 commit
  23. 17 Jul, 2017 1 commit
  24. 11 Jul, 2017 1 commit
  25. 06 Jul, 2017 1 commit
  26. 05 Jul, 2017 1 commit
  27. 29 Jun, 2017 2 commits
  28. 26 Jun, 2017 1 commit
  29. 19 Jun, 2017 1 commit
  30. 04 Jun, 2017 1 commit
  31. 28 May, 2017 1 commit
  32. 24 May, 2017 2 commits
  33. 07 Apr, 2017 1 commit
  34. 16 Mar, 2017 1 commit
  35. 28 Feb, 2017 1 commit