GitLab Next

Merged

Opened Aug 30, 2016 by Marc Siegfriedt @mahcsigContributor10 of 10 tasks completed10/10 tasks

Step 1. Fetch and check out the branch for this merge request

git fetch "https://gitlab.com/mahcsig/gitlab-ce.git" "17350-multi-file-commit"
git checkout -b "mahcsig/gitlab-ce-17350-multi-file-commit" FETCH_HEAD

Step 2. Review the changes locally

Step 3. Merge the branch and fix any conflicts that come up

git fetch origin
git checkout "master"
git merge --no-ff "mahcsig/gitlab-ce-17350-multi-file-commit"

Step 4. Push the result of the merge to GitLab

git push origin "master"

Note that pushing to GitLab requires write access to this repository.

Tip: You can also checkout merge requests locally by following these guidelines.

API: Multi-file commit

Adds a new endpoint to the GitLab API allowing for commiting multiple files at once

When creating the tests I noticed that the call returns on the first validation error, should I update it so that the entire call is validated and return all errors, or is failing at the first issue acceptable?
What should be returned? The current file APIs return the branch and file_path. This call can have multiple files so it's not as clear, currently it just returns the branch.

When using the API to work with the repository, the commit log gets cluttered with one commit per file.

Assignee

Assign to

8.13

Milestone

Assign milestone

Time tracking

Reference: gitlab-org/gitlab-foss!6096

Source branch: 17350-multi-file-commit