Skip to content
GitLab
Next
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 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,331
    • Merge requests 1,331
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and 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.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #326168
Closed
Open
Issue created Mar 28, 2021 by Steve Mokris@smokris🐢Contributor

Add a custom commit message when applying batched suggestions

Release notes

Problem to solve

When applying a single MR suggestion, you can write a custom commit message. But when applying a batch of MR suggestions, the custom commit message dialog is not presented.

I noticed @jerasmus started work on this on !49102 (closed) a few months ago, but that MR was closed. I couldn't find an open issue tracking that feature, so I'm opening this one to make sure it doesn't get lost.

Related: #25486 (closed) and #25381 (closed)

Intended users

  • Sasha (Software Developer)

User experience goal

Proposal

Further details

This matters for my team's workflow since we have a custom update hook that requires commit messages to have a certain format. (The project-wide merge suggestion commit message template isn't adequate for this, since our custom update hook requires the corresponding issue number, which isn't one of the available variables for that template.)

Permissions and Security

  • Same permissions as for writing a custom commit message for a single suggestion

Documentation

  • Mention in a new subsection of https://docs.gitlab.com/ee/user/discussions/#suggest-changes

Availability & Testing

Available Tier

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references

Assignee
Assign to
Time tracking