Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab FOSS
GitLab FOSS
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1
    • Merge requests 1
  • Requirements
    • Requirements
    • List
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Merge requests
  • !18004

Merged
Created Mar 26, 2018 by Mark Fletcher@markglenfletcher🔴Maintainer8 of 13 tasks completed8/13 tasks

Allow merge requests related to a commit to be found via API

  • Overview 2
  • Commits 1
  • Pipelines 2
  • Changes 4

What does this MR do?

Allow merge requests related to a commit to be found via API

  • Original work for the web interface here:
  • https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/13713

Are there points in the code the reviewer needs to double check?

Why was this MR needed?

Please see:

  • https://gitlab.com/bjgopinath/release-changes/issues/2

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

  • Changelog entry added, if necessary
  • Documentation created/updated
  • API support added
  • Tests added for this feature/bug
  • Review
    • Has been reviewed by UX
    • Has been reviewed by Frontend
    • Has been reviewed by Backend
    • Has been reviewed by Database
  • Conform by the merge request performance guides
  • Conform by the style guides
  • Squashed related commits together
  • Internationalization required/considered
  • End-to-end tests pass (package-and-qa manual pipeline job)

What are the relevant issue numbers?

Edited Mar 26, 2018 by Mark Fletcher
Assignee
Assign to
Reviewer
Request review from
10.7
Milestone
10.7 (Past due)
Assign milestone
Time tracking
Source branch: expose-commits-mr-api