An error occurred fetching the project authors.
  1. 13 Apr, 2020 1 commit
  2. 08 Apr, 2020 1 commit
  3. 24 Mar, 2020 1 commit
  4. 17 Mar, 2020 1 commit
  5. 13 Mar, 2020 1 commit
  6. 10 Mar, 2020 1 commit
  7. 17 Feb, 2020 1 commit
  8. 03 Feb, 2020 1 commit
  9. 29 Jan, 2020 1 commit
  10. 23 Jan, 2020 1 commit
  11. 21 Jan, 2020 1 commit
    • Patrick Bajao's avatar
      Check mergeability of MR asynchronously · 8c01b8e7
      Patrick Bajao authored
      Executing `MergeRequests::MergeabilityCheckService#execute` can be
      time consuming and can likely cause a request to timeout.
      
      Moving its execution asynchronously via `#async_execute` will help
      in ensuring page and API requests that needs it can load faster.
      8c01b8e7
  12. 09 Jan, 2020 1 commit
    • Yorick Peterse's avatar
      Remove deployment feature flags · 45bfb5be
      Yorick Peterse authored
      This removes the feature flags used for recording deployed merge
      requests and for displaying this data in the merge request widget. Both
      features are deemed stable now, so we no longer need these feature
      flags.
      45bfb5be
  13. 08 Jan, 2020 1 commit
    • Paul Slaughter's avatar
      Fix Content-Security-Policy with Sourcegraph · 20f0bb08
      Paul Slaughter authored
      Also renamed SourcegraphGon to SourcegraphDecorator
      
      **Note:**
      
      - If CSP values are set, it uses the values from
      default-src if connect-src is not available. This
      way the intention of the CSP config remains intact.
      20f0bb08
  14. 21 Dec, 2019 1 commit
  15. 11 Dec, 2019 1 commit
    • Thomas Randolph's avatar
      Integrate with single diff type feature flag · 98f1ce3e
      Thomas Randolph authored
      This commit pushes the single_mr_diff_view 
      feature flag into the glFeatures JavaScript 
      object as soon as the merge requests controller 
      starts up.
      
      Because that feature flag is needed in the Vuex 
      actions and mutations, as soon as the Diffs Vue 
      app starts, it also takes that feature flag and puts 
      it into state.
      98f1ce3e
  16. 04 Dec, 2019 1 commit
    • Phil Hughes's avatar
      Move behind a feature flag · 2662b4b0
      Phil Hughes authored
      Added a feature flag so that if the async side stops working we can
      easily revert back to original behaviour
      2662b4b0
  17. 28 Nov, 2019 1 commit
    • Yorick Peterse's avatar
      Use explicitly tracked deployments for MR widgets · 94e5f04a
      Yorick Peterse authored
      When displaying the deployments of a merge request in the MR widget, we
      used to rely on the latest CI pipeline to determine what the deployment
      was. In this commit we add the ability to use the table
      "deployment_merge_requests" to display the deployments of a merge
      request. This way the data displayed remains the same, regardless of the
      state of any CI pipelines.
      
      These changes are currently hidden behind the
      "deployment_merge_requests_widget" project feature flag. We do not
      reuse the existing deployments feature flag, as we still want to record
      merge requests even if the UI is not able to display the data properly.
      94e5f04a
  18. 19 Nov, 2019 1 commit
  19. 15 Nov, 2019 3 commits
    • Paul Slaughter's avatar
      Sourcegraph finishing touches · aa616eea
      Paul Slaughter authored
      - Reverting project policy change
      - Cleaning lints
      - Adding specs
      - Updating FE to load sourcegraph only on necessary views
      aa616eea
    • Bob Van Landuyt's avatar
      Validate the diff head sha when merging · 7d10d4aa
      Bob Van Landuyt authored
      This compares the `MergeRequest#diff_head_sha` before squashing or
      merging to a sha passed by the caller. If the `diff_head_sha` changed,
      this means that the branch was updated since the merge was scheduled.
      
      The `diff_head_sha` is the one passed to gitaly for merging or
      squashing. So validating it right before performing the merge rather
      than only in the controller would prevent the
      `MergeRequests::RefreshService` from changing it between scheduling
      the merge and actually merging.
      7d10d4aa
    • Igor Drozdov's avatar
      Load limited number of diff commits from database · dc3aa6c6
      Igor Drozdov authored
      Also preload users and latest pipeline for the correct ref
      dc3aa6c6
  20. 07 Nov, 2019 1 commit
    • Pulkit Sharma's avatar
      Move DAST reports comparison logic to backend · c69b2145
      Pulkit Sharma authored
      Add dast_report to authorized endpoints
      
      Update merge_request.rb#has_dast_reports? to check on dast_reports
      
      Update FactoryBot params, use frozen_string_literal: true
      
      Update specs according to the new fixture
      c69b2145
  21. 04 Nov, 2019 1 commit
    • Nathan Friend's avatar
      Add "release" filter to merge request search page · fbc7d1d9
      Nathan Friend authored
      This commit adds a new filter - "release" - to the merge request search
      page. This filter takes a tag name (i.e. v1.2) as a parameter and
      appends a URL parameter to the search query like "release_tag=v1.2".
      fbc7d1d9
  22. 21 Oct, 2019 3 commits
    • allison.browne's avatar
      c77bb71c
    • Stan Hu's avatar
      Time limit database lock when rebasing a merge request · cce486da
      Stan Hu authored
      `MergeRequest#rebase_async` can lock indefinitely with a SELECT FOR
      UPDATE call. If an update is idle in transaction or another rebase
      attempts to run, `MergeRequest#rebase_async` could queue indefinitely or
      until statement timeouts are triggered.
      
      To limit the impact of this operation, we now just bail out after 5 s if
      we can't get the lock. The user will see an error message if this
      happens.
      
      Part of https://gitlab.com/gitlab-org/gitlab/issues/30528
      cce486da
    • Fabio Pitino's avatar
      Expose arbitrary artifacts via MR widget · 5c168885
      Fabio Pitino authored
      * Allow user to specify `artifacts:expose_as` in CI config
      * Save :has_exposed_artifacts in job metadata for queries
      * Find exposed artifacts in build metadata model
      * Expose API endpoint for frontend to fetch data
      
      Fix unlrelated controller specs
      
      Use default has_exposed_artifacts NULL
      
      Avoid using a background migration to change NULL
      to false. It's not needed.
      
      Feedback from review
      
      * add links to issue for follow up refactoring
      * preload job artifacts and metadata associations
      * merge DisallowedRegexInArrayValidator into existing
      ArrayOfStringsValidator
      * other minor changes
      
      Rename params to match frontend code
      
      Feedback from review
      
      Feedback from review
      5c168885
  23. 15 Oct, 2019 1 commit
  24. 09 Oct, 2019 1 commit
  25. 24 Sep, 2019 1 commit
    • Paul Slaughter's avatar
      Fix cannot merge badge showing bug in dropdown · 99f65fd5
      Paul Slaughter authored
      **Why was this happening?**
      The `can_merge` flag is appropriately sent, but we
      don't get information on selected users from the BE.
      Instead, this information comes from the HAML, which
      wasn't setting `can_merge`.
      99f65fd5
  26. 18 Sep, 2019 1 commit
    • Erick Bajao's avatar
      Batch load pipelines instead of statuses · ecf18fcf
      Erick Bajao authored
      Instead of preloading the status, we now preload the
      latest pipelines instead for each commit. This gives us more
      flexibility on how to display the status.
      
      This also helps us avoid passing the current_user deep through
      the model methods. Best to call the detailed_status in the
      view/presentation layer.
      
      We also extracted commit's pipeline behavior into its own class.
      This is to better isolate and organize the pipeline related behavior
      of the Commit object.
      
      Moving the pipeline behavior into its own class resulted
      to a lot of breaking changes though. So instead of always having to
      create your own instance of a CommitWithPipeline, we're just gonna
      use the same commit object but just delegate the pipeline related
      calls to the CommitWithPipeline instance.
      ecf18fcf
  27. 17 Sep, 2019 1 commit
  28. 13 Sep, 2019 1 commit
    • Oswaldo Ferreira's avatar
      Improve the performance for MR discussions load · 71a1a017
      Oswaldo Ferreira authored
      It considerably improves the query for preloading MR
      discussion diffs for:
      
      1. MR diff comments (made at Diffs tab; presented at the main MR page)
      2. Comments on commits being listed at the MR
      
      Additionally, it also prevents a second similar query that was
      unnecessarily being made.
      71a1a017
  29. 12 Sep, 2019 1 commit
  30. 28 Aug, 2019 1 commit
  31. 22 Aug, 2019 2 commits
  32. 21 Aug, 2019 2 commits
  33. 20 Aug, 2019 1 commit
  34. 12 Aug, 2019 1 commit