An error occurred fetching the project authors.
  1. 03 Oct, 2015 1 commit
  2. 07 Jul, 2015 2 commits
  3. 19 Jun, 2015 1 commit
  4. 27 May, 2015 1 commit
  5. 25 May, 2015 1 commit
  6. 30 Apr, 2015 1 commit
    • Dominik Sander's avatar
      Group milestones by title in the dashboard and all other issue views · e6ee8d0e
      Dominik Sander authored
      This groups milestones by title for issue views like it has been done for
      the milestone dashboard/project overview. Before milestones with the
      same title would show up multiple times in the filter dropdown and one could
      only filter per project and milestone. Now the milestone filter is based
      on the title of the milestone, i.e. all issues marked with the same
      milestone title are shown.
      e6ee8d0e
  7. 27 Mar, 2015 2 commits
  8. 01 Jan, 2015 1 commit
  9. 05 Dec, 2014 1 commit
  10. 27 Oct, 2014 1 commit
  11. 02 Sep, 2014 1 commit
  12. 30 Jul, 2014 2 commits
  13. 29 Jul, 2014 1 commit
  14. 05 Jun, 2014 1 commit
  15. 24 Mar, 2014 1 commit
    • Robert Speicher's avatar
      Fix deprecation warning output · a87f0376
      Robert Speicher authored
      Removes the following from test output:
      
        DEPRECATION WARNING: It looks like you are eager loading table(s) (one
        of: merge_requests, projects) that are referenced in a string SQL
        snippet. For example:
      
            Post.includes(:comments).where("comments.title = 'foo'")
      
        Currently, Active Record recognizes the table in the string, and knows
        to JOIN the comments table to the query, rather than loading comments in
        a separate query. However, doing this without writing a full-blown SQL
        parser is inherently flawed. Since we don't want to write an SQL parser,
        we are removing this functionality. From now on, you must explicitly
        tell Active Record when you are referencing a table from a string:
      
            Post.includes(:comments).where("comments.title =
        'foo'").references(:comments)
      
        If you don't rely on implicit join references you can disable the
        feature entirely by setting
        `config.active_record.disable_implicit_join_references = true`.
      a87f0376
  16. 25 Feb, 2014 1 commit
  17. 20 Feb, 2014 1 commit
  18. 10 Feb, 2014 1 commit
  19. 03 Feb, 2014 2 commits
  20. 31 Jan, 2014 1 commit
  21. 16 Jan, 2014 1 commit
  22. 15 Jan, 2014 1 commit