Is it possible to override GitLab syntax for shorthand links #2448
-
Referring to https://facelessuser.github.io/pymdown-extensions/extensions/magiclink/#shorthand-links
I generate documentation from PR summaries from github, so in those summaries we use the |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
I'm not sure I understand the request. Can you clarify exactly what you are asking? GitHub will resolve GitLab is very particular and requires So, can you explain a bit better why your situation requires a change and how it does not conflict with the above statements? I generally try to provide a generic approach that fits the broader audience. It can be difficult at times to justify the effort to add in support for niche cases that maybe only 1% of users might utilize. I'm open to considering such work on a case-by-case basis, but I need to understand everything and get a feel for how much it would be used by the wider community. |
Beta Was this translation helpful? Give feedback.
I'm not sure I understand the request. Can you clarify exactly what you are asking?
GitHub will resolve
#
as an issue. When you click an issue link, GitHub will redirect to PRs or Issues depending on the real context. In short, GitHub does not require!
for Pull/Merge requests, but can optionally be used if you like the GitLab-like separation.GitLab is very particular and requires
#
or!
(within their app) to create links that are either issues or merge requests. An issue URL with a merge request ID will not be redirected merge requests but will go to issues and fail, or find an issue with that number, not matching the intent. So, in order to intelligently tell what a user means in their…