API link between commit and merge request: get MR id in commit data

Description

Hi,

I'm using the gitlab api for developping devops tools in C#. For my current tool, I need to determine the MRs merged since the last tag. I've tried to do that by date, but the date of the tag is the date of the commit and there is no refference to the MR, neither in the tag nor in the commit. Since you can get the commits for a given MR, i thought the reverse was possible. However, i haven't found any way to do that. As far as i can see the only way to find the MR of a certain commit is to go through all the project's MRs and search through the commit list of each MR for the commit in question. This seems very suboptimal to me...

Proposal

Since a commit belongs to a unique MR, could you please add the MR id or iid in the commit data? So that a GET on /repository/commits/:id would return something like this :

{
  "id": "c56ffd183cfea378e6739309f062735b7e0a940f",
  "short_id": "c56ffd18",
  "mr_id": "1234",
  "title": "my title",
  "author_name": "author",
  "author_email": "author.email@mymail.com",
  "created_at": "2016-08-08T14:56:44.000+02:00",
  "message": "my message",
  "parent_ids": [
    "0df292af73541ec55fa7447bc128ab1da210ebca",
    "0578adfc39fd07aa653bee3b08f0318a26010073"
  ],
  "committed_date": "2016-08-08T14:56:44.000+02:00",
  "authored_date": "2016-08-08T14:56:44.000+02:00",
  "stats": {
    "additions": 435,
    "deletions": 26,
    "total": 461
  },
  "status": "failed"
}

If the commit has no MR then the mr_id could be empty.

Another interesting feature would be to have the merge date for an MR.

Thanking you in advance.

Links / references

I've found a similar question on stackoverflow, but no answer alas! http://stackoverflow.com/questions/33168209/gitlab-get-merge-request-from-a-commit-id

Added ~13884 feature proposal repository labels

Mentioned in merge request !6473 (closed)

mentioned in issue #34640 (closed)

moved to gitlab#6109

Hey!

GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current gitlab-ce repository will become a read-only mirror, without any proprietary code. All development is moved to the current gitlab-ee repository, which we will rename to just gitlab in the coming weeks. As part of this migration, issues will be moved to the current gitlab-ee project.

If you have any questions about all of this, please ask them in our dedicated FAQ issue.

https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

You can also find more information here:

• https://gitlab.com/gitlab-org/gitlab-ee/issues/13304
• https://about.gitlab.com/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/

Frequently Asked Questions

For an up to date list of questions and answers, please take a look at https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

What will we do with the repository names?

https://gitlab.com/gitlab-org/gitlab-ee/ will become https://gitlab.com/gitlab-org/gitlab, and https://gitlab.com/gitlab-org/gitlab-ce will become https://gitlab.com/gitlab-org/gitlab-foss.

Why rename gitlab-ce to gitlab-foss?

Using "gitlab" and "gitlab-ce" would be confusing, so we decided to rename gitlab-ce to gitlab-foss to make the purpose of this FOSS repository more clear

I created a merge requests for CE, and this got closed. What do I need to do?

You will need to create a merge request at https://gitlab.com/gitlab-org/gitlab-ee/. This link will eventually redirect to https://gitlab.com/gitlab-org/gitlab.

How does the licensing work in this new setup?

Everything in the ee/ directory is proprietary. Everything else is free and open source software. If your merge request does not change anything in the ee/ directory, the process of contributing changes is the same as when using the gitlab-ce repository.

Will you accept merge requests on the gitlab-ce/gitlab-foss project after it has been renamed?

No. Merge requests submitted to this project will be closed automatically.

Will I still be able to view old issues and merge requests in gitlab-ce/gitlab-foss?

Yes.

How will this affect users of GitLab CE using Omnibus?

No changes will be necessary, as the packages built remain the same.

How will this affect users of GitLab CE that build from source?

Once the project has been renamed, you will need to change your Git remotes to use this new URL. GitLab will take care of redirecting Git operations so there is no hard deadline, but we recommend doing this as soon as the projects have been renamed.

Where can I see a timeline of the remaining steps?

https://gitlab.com/gitlab-org/gitlab-ee/issues/13304

Will community contributions submitted to the new "gitlab" repository be available in the new gitlab-foss repository?

Yes, these changes will be synced to gitlab-foss automatically, several times per day.

locked this issue