1. 28 Mar, 2019 2 commits
  2. 27 Mar, 2019 4 commits
  3. 26 Mar, 2019 2 commits
  4. 25 Mar, 2019 2 commits
  5. 22 Mar, 2019 3 commits
  6. 21 Mar, 2019 6 commits
    • Luke Duncalfe's avatar
      Handle blank projects in CommitCollection#enrich! · 4afeae40e9be
      Luke Duncalfe authored
      A project is needed in order to fetch data from gitaly. Projects can be
      absent from commits in certain rare situations (like when viewing a MR
      of a deleted fork). In these cases, assume that the enriched data is not
      needed.
      
      See this comment:
      
      https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/26144#note_152191106
      
      "It's led to a dilemma about where to "fix" this in code. I'm going
      to fix it by allowing CommitCollection#enrich! to just return unenriched
      commits when a project is missing, essentially "silently failing". I
      hope this is the right decision. It's going with the assumption that
      calls in these situations in the future are not needing the full data.
      The alternative would be to allow CommitCollection#enrich! to still
      error, but handle it in the methods that call #enrich!, however that
      might lead to brittleness in future when working with project-less MRs."
      4afeae40e9be
    • Luke Duncalfe's avatar
      Enrich commits with full data in CommitCollection · abd2ee50323c
      Luke Duncalfe authored
      Allow incomplete commit records to load their full data from gitaly.
      
      Commits can be based on a Hash of data retrieved from PostgreSQL, and
      this data can be intentionally incomplete in order to save space.
      
      A new method #gitaly? has been added to Gitlab::Git::Commit, which
      returns true if the underlying data source of the Commit is a
      Gitaly::GitCommit.
      
      CommitCollection now has a method #enrich which replaces non-gitaly
      commits in place with commits from gitaly.
      
      CommitCollection#without_merge_commits has been updated to call this
      method, as in order to determine a merge commit we need to have parent
      data.
      
      Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/58805
      abd2ee50323c
    • Nathan Friend's avatar
      Update merge request widget pipeline block · 311227fd8124
      Nathan Friend authored
      This commit updates the pipeline block that appears on the merge request
      page to include information that will be exposed by the API as part of
      the post-merge pipeline feature.
      311227fd8124
    • Sam Bigelow's avatar
      Add merge request popover with details · 9714f374b8a2
      Sam Bigelow authored
      - Show pipeline status, title, MR Status and project path
      - Popover attached to gitlab flavored markdown everywhere, including:
        + MR/Issue Title
        + MR/Issue description
        + MR/Issue comments
        + Rendered markdown files
      9714f374b8a2
    • Sean McGivern's avatar
      Revert "Merge branch... · 9ba9fc06dccc
      Sean McGivern authored
      Revert "Merge branch '58805-allow-incomplete-commit-data-to-be-fetched-from-collection' into 'master'"
      
      This reverts merge request !26144
      9ba9fc06dccc
    • James Fargher's avatar
      Update dashboards to additionally use new environment selector · fbf36cc66828
      James Fargher authored
      Deploy boards now will check for app.gitlab.com/env and
      app.gitlab.com/app
      fbf36cc66828
  7. 20 Mar, 2019 9 commits
  8. 19 Mar, 2019 4 commits
  9. 18 Mar, 2019 3 commits
  10. 17 Mar, 2019 1 commit
  11. 14 Mar, 2019 2 commits
  12. 13 Mar, 2019 2 commits