Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #9613

Closed
Open
Created Sep 09, 2015 by Administrator@rootOwner

Relative link is not relative to current path, but relative to root of project

Created by: Rufflewind

Consider a repository with this structure:

/
  /somedir
    /somedir/file1.md
    /somedir/file2.md
  /.gitignore
  /README.md

If the Markdown document file1.md contains a relative link like this:

[some link](file2.md)

It doesn't work on GitLab because the link will refer to /file1.md in the root directory (which doesn't exist).

This behavior differs from that of GitHub and BitBucket, both of which will (correctly) resolve to /somedir/file1.md.

(Tested on GitLab.com in Chromium on Arch Linux x86-64)

Assignee
Assign to
Time tracking