Github wiki's should support proper directory pathing for linking files

[tenzinhl]

This has been brought up at various points for a while. Basically: folderizing wiki files (markdown files) in Github is a bit jank. I appreciate that progress has been made (folders work), but it feels far more intuitive to link files through appropriate file paths (either relative or absolute).

I admit part of the motivation for this is that this way wiki repos will be more compatible across Gitlab and Github.

This has been brought up before:
https://stackoverflow.com/questions/11088285/github-wiki-directories

It's unclear from the docs how to properly link to pages in subfolders:
https://docs.github.com/en/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages

How to link files in subfolders in Github wikis:
https://github.com/tajmone/github-tests/wiki/subfolders#the-right-way-to-link

^What I'm requesting is that the Github wiki renderer (not sure if that's the right term) would allow [Link To Page In Subdirectory](subdirectory/page.md) syntax to work.

[nathanjrobertson]

Please implement this. I've just hit this - when you're trying to store a non-trivial amount of documentation in a GitHub wiki, the number of files in the single folder gets out of hand. Directories existed on 1970's UNIX. Please add them to 2020's GitHub.

[rycaputo]

agree

[iDeliverDev]

I agree, it gets in the way of using wikis to their full potential.
👍

[wonjin-dev]

[KJMascarenhas]

This is truly a major deficiency since it does not allow you to simply use the standard Markdown files stored in the repo (with their correct links) within the Wiki too and forces you to either create a whole set of duplicated documentation or find a creative way to perform some link conversion to make this work.

What would be even better is to somehow have that Wiki repo be able to directly reference the Markdown files that already exist in the main repo. This would avoid implementing an automatic sync Actions Workflow between the Main repo and Wiki.

[alexgalkin]

Also missing this feature

[ItsJayPM]

Alas, I am here to agree, why the heck isn't this a thing in 2025?

[luxoddgames]

Yep same... need this done

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐