Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 43,810
    • Issues 43,810
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,418
    • Merge requests 1,418
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • 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.org
  • GitLabGitLab
  • Issues
  • #20263
Closed
Open
Created Nov 27, 2017 by Dispix@dispix

Merge commit template

Description

With the current merge request system, little attention is paid to the merge commit message apart from references to things like issues or other merge requests. However, the merge commit could expose much more information about the role of the merge request and/or the branches that are being merged.

Currently, you can create templates for merge requests in order to enforce good practices. This can be used to decorate the commit message by including the description but this is more or less a "hack".

Proposal

Allow the creation of merge commit template(s), just like you can create markdowns and save them in .gitlab/merge_request_templates. As the commit message has information related to the merge request, a format like handlebars may be more appropriate to allow syntaxes such as Merge branch {{MERGE_BRANCH}} into {{MERGE_TARGET}}.

Assignee
Assign to
Time tracking