From 4a1670abf6ce552586efd812486980a70eb6fdf0 Mon Sep 17 00:00:00 2001 From: MilagrosMarin Date: Tue, 5 May 2026 18:21:25 +0200 Subject: [PATCH] docs: use relative path for README pipeline image MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The absolute raw.githubusercontent.com URL is served via GitHub's camo image proxy, which caches aggressively — so even after #1448 refreshed images/pipeline.png, the rendered README kept showing the old image. Switching to a relative path lets GitHub serve the image directly from the current commit, so the new illustration appears immediately and future updates to the file render without cache hiccups. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 945d2ff4b..75e391ee3 100644 --- a/README.md +++ b/README.md @@ -69,7 +69,7 @@ conda install -c conda-forge datajoint ## Example Pipeline -![pipeline](https://raw.githubusercontent.com/datajoint/datajoint-python/master/images/pipeline.png) +![pipeline](images/pipeline.png) **Cite DataJoint:** [Yatsenko et al., 2026](https://arxiv.org/abs/2602.16585) — RRID: [SCR_014543](https://scicrunch.org/resolver/SCR_014543)