Skip to content
Snippets Groups Projects
  1. Dec 12, 2019
  2. Nov 22, 2019
  3. Nov 12, 2019
  4. Nov 04, 2019
  5. Oct 16, 2019
  6. Sep 23, 2019
  7. Sep 11, 2019
    • Filipa Lacerda's avatar
      Enables Run Pipeline button to be rendered · 48b98b58
      Filipa Lacerda authored
      In the Merge Request view, under pipelines tab
      the user can see a run pipeline button
      
      Adds axios post request to button click
      
      Adds the logic to handle the user click,
      refresh the table and disable the button while thee
      request is being made
      
      Updates UI for desktop and mobile
      
      Adds specs
      Regenerates potfile
      
      Follow-up after review
      
      Uses .finally to avoid code repetition
      48b98b58
  8. Sep 09, 2019
  9. Aug 19, 2019
  10. Jul 09, 2019
    • Tim Zallmann's avatar
      Updates on success of an MR the count on top and in other tabs · b9e52612
      Tim Zallmann authored
      New API endpoint for merge request count
      Updates all open tabs at the same time with one call
      Restructured API response
      
      API response changed to 401 if no current_user
      
      Added API + JS specs
      
      Fix for Static Check
      
      Updated Count on Open/Close, Assign/Unassign of MR's
      
      Checking if MR Count is refreshed
      
      Added # frozen_string_literal: true to spec
      
      Added Changelog
      b9e52612
  11. Jun 19, 2019
  12. May 29, 2019
  13. Apr 24, 2019
  14. Mar 04, 2019
    • Denys Mishunov's avatar
      Extended Web IDE API to get MRs for a certain branch in a project · a1b0b3e4
      Denys Mishunov authored
       New `Api.projectMergeRequests` allows:
       - to query for all MRs on a project without specifying `mergeRequestId`
       - to filter the returned MRs using parameters from
       https://bit.ly/2H7We4V
      
       The new API request is used for fetching information about MRs
       associated with a particular branch in Web IDE to have IdeSidebar
       behave consistently in both scenarios:
       - getting to a branch from and MR (where we already have info about
       relevant MR), or
       - getting to a branch somehow differently directly
      
      For cases where there are several merge requests that the current branch
      is associated with, mark the most recent one as 'current'
      
      Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/49663
      a1b0b3e4
  15. Feb 04, 2019
  16. Dec 21, 2018
  17. Dec 20, 2018
  18. Dec 13, 2018
  19. Dec 08, 2018
  20. Dec 05, 2018
  21. Nov 28, 2018
  22. Nov 27, 2018
  23. Oct 05, 2018
  24. Oct 04, 2018
  25. Aug 17, 2018
  26. Aug 07, 2018
  27. Jul 05, 2018
  28. Jul 02, 2018
  29. Jun 27, 2018
  30. May 25, 2018
  31. May 24, 2018
  32. May 22, 2018
  33. Mar 28, 2018
  34. Mar 09, 2018
  35. Feb 22, 2018
Loading