Relative image paths in markdown files are not resolved #7

Closed@k33g opened this issue Sep 15, 2026 · 3 comments

@k33g opened this issue · Sep 15, 2026
Voici la traduction :

I have a project called work-with-llama-cpp in the docker-agent-cookbook organization. In the README.md, if I want to include images from the repository's /assets folder, I can't use the following path:

![01-llamacpp](./assets/01-llamacpp.png)

Instead, I have to use the full path starting from the organization:

![01-llamacpp](/docker-agent-cookbook/work-with-llama-cpp/raw/main/assets/01-llamacpp.png)

repository: https://rickub.com/docker-agent-cookbook/work-with-llama-cpp/tree/main
edited
@ogirardot · Sep 18, 2026
on it thx
@ogirardot · Sep 18, 2026
Fixed by !331, merged and deployed.

Relative image destinations in READMEs and markdown file views now resolve to the repo's raw endpoint at the ref being viewed — your repo's README now renders ![01-llamacpp](./assets/01-llamacpp.png) as /docker-agent-cookbook/work-with-llama-cpp/raw/main/assets/01-llamacpp.png, and the hand-written absolute path from this issue keeps working unchanged. The ./assets/... form works from the repo root, and images inside a docs/ markdown file resolve relative to that file's own directory.

Scope note: relative images are rewritten; relative links ([text](./docs/x.md)) are intentionally left for a follow-up — a link should open the tree/blob view, and choosing between tree and blob needs to know whether the target is a file or a directory (one engine lookup per link at render time).
@ogirardot · Sep 18, 2026
it's fixed and deployed, thanks for the report