Skip to content

GitLab Next

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar

GitLab 15.0 is launching on May 22! This version brings many exciting improvements, but also removes deprecated features and introduces breaking changes that may impact your workflow. To see what is being deprecated and removed, please visit Breaking changes in 15.0 and Deprecations.

  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Merge requests
  • !6096

API: Multi-file commit

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged
Marc Siegfriedt requested to merge mahcsig/gitlab-ce:17350-multi-file-commit into master Aug 30, 2016
  • Overview 139
  • Commits 1
  • Pipelines 22
  • Changes 10

What does this MR do?

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

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

  • 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.

Why was this MR needed?

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

Does this MR meet the acceptance criteria?

  • CHANGELOG entry added
  • Documentation created/updated
  • API support added
  • Tests
    • Added for this feature/bug
    • All builds are passing
  • Conform by the style guides
  • Branch has no merge conflicts with master (if you do - rebase it please)
  • Squashed related commits together

What are the relevant issue numbers?

Closes #17350 (closed)

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: 17350-multi-file-commit