BigW Consortium Gitlab

  1. 12 Mar, 2015 1 commit
    • Implement merge requests search · 80b2f3fb
      Dmitriy Zaporozhets authored
      It is same search like we have at issues page. It allows to quickly
      filter merge requests based on title or desription. I copy-pasted some
      js code from Issues.js. In future search (filtering) logic should be
      refactoed into one class for merge requests and issues
  2. 20 Feb, 2015 1 commit
  3. 19 Feb, 2015 2 commits
  4. 23 Dec, 2014 2 commits
  5. 05 Dec, 2014 1 commit
  6. 02 Dec, 2014 1 commit
  7. 20 Nov, 2014 1 commit
  8. 03 Oct, 2014 1 commit
  9. 10 Jul, 2014 1 commit
  10. 14 Jun, 2014 2 commits
  11. 29 May, 2014 1 commit
  12. 13 May, 2014 1 commit
  13. 20 Feb, 2014 1 commit
  14. 13 Feb, 2014 2 commits
  15. 14 Jan, 2014 3 commits
  16. 30 Dec, 2013 1 commit
  17. 09 Oct, 2013 1 commit
  18. 15 Aug, 2013 1 commit
    • More specific empty state message wording · 4b91ffca
      Henry Smith authored
      I've changed all the instances of "Nothing to show here" to specifically mention
      the name of the entity of which there are none to show. This makes for a
      slightly smoother reading experience.
  19. 12 Aug, 2013 1 commit
  20. 10 Aug, 2013 1 commit
  21. 01 Aug, 2013 1 commit
  22. 13 Jul, 2013 2 commits
  23. 23 Jun, 2013 1 commit
  24. 06 Apr, 2013 2 commits
  25. 30 Jan, 2013 1 commit
  26. 29 Jan, 2013 1 commit
  27. 21 Jan, 2013 1 commit
  28. 08 Jan, 2013 1 commit
  29. 05 Jan, 2013 2 commits
  30. 18 Dec, 2012 1 commit
  31. 26 Oct, 2012 1 commit
    • Add Milestone information in Merge Requests · a7d08169
      Sergio Visinoni authored
      Step 1:
      * Add milestone_id in the model for merge_requests
      * Make it possible to create or update a Merge Request with an attached
        Milestone detail
      * Add the possibility to filter by Milestone and / or Assignee in the
        Merge Requests listing page