Commit message templates

WVS uses commit templates to create default messages for specific types of commits. These templates encourage commit messages to follow a particular format, or contain specific information. Users can override these templates when merging a merge request.

Commit templates use syntax similar to the syntax for review suggestions.

Configure commit templates

Change the commit templates for your project if the default templates don’t contain the information you need.

Prerequisite:

  • You must have at least the Maintainer role for a project.

To do this:

  1. On the top bar, select My Projects > View All Projects and find your project.
  2. On the left sidebar, select Project Settings > General and expand Merge requests.
  3. Depending on the type of template you want to create, scroll to either Merge commit message template or Squash commit message template.
  4. For your desired commit type, enter your default message. You can use both static text and variables. Each template is limited to a maximum of 500 characters, though after replacing the templates with data, the final message may be longer.
  5. Select Save changes.

Default template for merge commits

The default template for merge commit messages is: 

Merge branch '%{source_branch}' into '%{target_branch}'

%{title}

%{issues}

See merge request %{reference}

Default template for squash commits

If you have configured your project to squash commits on merge, WVS creates a squash commit message with this template: 

%{title}

Supported variables in commit templates

Commit message templates support these variables:

Variable Description Output example
%{source_branch} The name of the branch being merged. my-feature-branch
%{target_branch} The name of the branch that the changes are applied to. main
%{title} Title of the merge request. Fix tests and translations
%{issues} String with phrase Closes <issue numbers>. Contains all issues mentioned in the merge request description that match issue closing patterns. Empty if no issues are mentioned. Closes #465, #190 and #400
%{description} Description of the merge request. Merge request description.
Can be multiline.
%{reference} Reference to the merge request. group-name/project-name!72359
%{first_commit} Full message of the first commit in merge request diff. Update README.md
%{first_multiline_commit} Full message of the first commit that’s not a merge commit and has more than one line in message body. Merge request title if all commits aren’t multiline. Update README.md

Improved project description in readme file.
%{url} Full URL to the merge request. https://wvs.io/wvs-org/wvs/-/merge_requests/1
%{approved_by} Line-separated list of the merge request approvers. Approved-by: Samantha Jones <sjones@example.com>
Approved-by: Joe Yu <jyu@example.com>
%{merged_by} User who merged the merge request. Alex Smith <asmith@example.com>
%{co_authored_by} Names and emails of commit authors in a Co-authored-by Git commit trailer format. Limited to authors of 100 most recent commits in merge request. Co-authored-by: Zoe Green <zgreen@example.com>
Co-authored-by: Mike Jordan <mjordan@example.com>
%{all_commits} Messages from all commits in the merge request. Limited to 100 most recent commits. Skips commit bodies exceeding 100KiB and merge commit messages. * Feature introduced

This commit implements feature
Changelog:added

* Bug fixed

* Documentation improved

This commit introduced better docs.

Any line containing only an empty variable is removed. If the line to be removed is both preceded and followed by an empty line, the preceding empty line is also removed.

After you edit a commit message on an open merge request, WVS will not automatically update the commit message again. To restore the commit message to the project template, reload the page.