Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 55.4k
    • Issues 55.4k
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1.6k
    • Merge requests 1.6k
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #13001
Closed
Open
Issue created Jul 23, 2019 by Shinya Maeda@shinya.maeda💡Maintainer

Support "squash and merge" in Merge Train

Problem to solve

Currently, Merge Train doesn't allow users to choose squash option. It could be a deal-breaker for some users. We should consider supporting squash and merge.

screenshot_17

Intended users

Developers

Permissions and Security

To squash and merge pull requests, you must have write permissions in the repository, and the repository must allow squash merging.

These actions should be logged to audit log

Feature Flag

This feature is implemented behind merge_train_new_stale_check feature flag and enabled by default. Once we've confirmed the feature is deemed stable, we remove the feature flag.

Links and references

MRs:

  • Preserve merge train rows after merge !19864 (merged)
  • Proactively marking stale status in merge train !19434 (merged)
  • Documentation update (https://docs.gitlab.com/ee/ci/merge_request_pipelines/pipelines_for_merged_results/merge_trains/#requirements-and-limitations)
Edited Dec 10, 2019 by Shinya Maeda
Assignee
Assign to
Time tracking