Improve commit message drafting

Created on 30 July 2025, about 2 months ago

Problem/Motivation

I think the commit message drafting could be improved. Details are below.

Proposed resolution

Remaining tasks

User interface changes

  • Add the [#issue number] prefix.
  • Add a message-only format, so the message can be copied into the GitLab merge UI. This should be shown ahead of the CLI version, since the merge UI should be used more often. (Maybe have this be the only version, CLI users can input a message.)
  • Add a way to edit the main message? Or we can leave it for people to fix up after they paste. The issue or MR title will not always be a good commit message, so there should be a way to improve it.
  • Add a way to select feat/fix/etc without typing? It looks like the conventional commits spec is very flexible here, so we do want to keep this as a text field.
  • Nit: always remove any trailing newline in the message.
πŸ“Œ Task
Status

Active

Version

1.0

Component

User interface

Created by

πŸ‡ΊπŸ‡ΈUnited States drumm NY, US

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @drumm
  • First commit to issue fork.
  • Merge request !8Improvements to the git message β†’ (Merged) created by fjgarlin
  • πŸ‡ͺπŸ‡ΈSpain fjgarlin

    The MR so far addresses:
    - Use no reply email
    - Parse issue ID (it was there but needed to use a different attribute)
    - Trim space
    - Message only (having message only and git command seem too repetitive, and a big use of space on issues with many contributors)

    Not addressed:
    - Editing the message: if the goal is for them to paste that into the merge UI, they should be able to edit it there I guess.
    - Conventional commits select vs input text: I first thought of dropdown, but yeah, it's pretty flexible, so I kept it as text input.

  • Pipeline finished with Skipped
    about 1 month ago
    #561631
  • πŸ‡ͺπŸ‡ΈSpain fjgarlin

    This is merged now.

    The email format used is: $email = $contributor_user->getAccountName() . '@' . $contributor_user->id() . '.no-reply.drupal.org';
    This avoids extra calls to the GitLab api to use alternative emails.

    Not addressed (from previous comment):
    - Editing the message: if the goal is for them to paste that into the merge UI, they should be able to edit it there I guess.
    - Conventional commits select vs input text: I first thought of dropdown, but yeah, it's pretty flexible, so I kept it as text input.

    I will mark it as fixed, but if we need to iterate on it or redefine things we can reopen or open a follow-up issue.

  • πŸ‡ΊπŸ‡ΈUnited States dww

    Thanks, these are all great improvements!

    Instead of reopening, I spawned a follow-up: ✨ Add a UI to change footer "token" values for each user Active

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024