Alternative "GL-" prefix for crosslinking issues
See #204877 (closed)
A minimalistic implementation of the alternative GL- issue prefix for text parsers only.
For example, a commit message which contains GL-1234 will be linked on GitLab as if it were using the regular reference notation #1234.
Commit on the Git client (Fork):
Same commit on GitLab:
It's up to debate whether the above discrepancy between the source (commit message, issue text, wiki content etc) and the rendered view of this source is problematic or not.
IMHO, it's not a problem because those using the alternative notation have good reason to do so and are aware of it. I'd rather stick to # as the prefix used consistently across all of GitLab for all rendered output as well as searches.
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Closes #204877 (closed)