Skip to content

Add support for alternative internal issue reference prefix "GL-"

What does this MR do and why?

Take two for a minimalistic implementation of the alternative GL- issue prefix.

The main use case are git commits which prefix their message with the issue ID:

  • #1234: My great commit –> won't work since git interprets the # as a comment
  • My great commit (#1234) -> works, but more more difficult to follow since the position of the ID varies
  • GL-1234: My great commit -> this MR

Similar alternative prefixes exist for JIRA and most notable GitHub using GH-. The proposed GL- prefix therefore complies with the principle of least surprise.

Commit on the Git client (Fork):

Screen_Shot_2020-02-11_at_19.36.30

Same commit on GitLab:

Screen_Shot_2020-02-11_at_19.39.08

The discrepancy between the commit message reported by git log and what's displayed on GitLab UI is not problematic. In fact, it's even desirable to always use the standard notation on GitLab UI for the sake of uniformity.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #204877 (closed)

Merge request reports