root for relative links
when using relative links, such as [relative links](foo)
this will always link to /${USERGROUP}/${PROJECT}/blob/master/foo
.
tested in
-
a markdown file in the repository, e.g. from
/${NAMESPACE}/${PROJECT}/blob/master/README.md
-
the wiki, e.g. from
/${NAMESPACE}/${PROJECT}/wikis/home
-
the issue tracker, e.g. from
/${NAMESPACE}/${PROJECT}/issues/1
so there is some relative-root rewriting in place which is probably what people want in most cases.
however, this also makes it hard to:
-
reference other pages from the project via relative links:
- the wiki (
../../wikis/home
??) - milestones, graphs,...
- the wiki (
it also makes it impossible to use relative links to reference to other projects
-
/${OTHERNAMESPACE}/${PROJECT2}
seems to resolve to/${NAMESPACE}/${PROJECT}/blob/master/${OTHERNAMESPACE}/${PROJECT2}
or to general gitlab pages, like [/help], which i want to resolve to https://${MYHOST}/help.
according to the GitLab Markdown reference there is no special meaning assigned to a trailing slash /
, which i would intuitively think of as the page root (or probably the project root, in which case there would be the need for a separate page root as well, e.g. //
)