From e6f4924c84532271a3899c5a8512dd3ef72ff144 Mon Sep 17 00:00:00 2001 From: Nick Dumas Date: Tue, 28 Feb 2023 14:50:24 -0500 Subject: [PATCH] Trying to match test case to reality --- .../blog/contents/notes/{demo-post => drone-and-hugo}/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename drone-plugins/sanitize-links/tmp/blog/contents/notes/{demo-post => drone-and-hugo}/index.md (99%) diff --git a/drone-plugins/sanitize-links/tmp/blog/contents/notes/demo-post/index.md b/drone-plugins/sanitize-links/tmp/blog/contents/notes/drone-and-hugo/index.md similarity index 99% rename from drone-plugins/sanitize-links/tmp/blog/contents/notes/demo-post/index.md rename to drone-plugins/sanitize-links/tmp/blog/contents/notes/drone-and-hugo/index.md index 81f46af..1175670 100644 --- a/drone-plugins/sanitize-links/tmp/blog/contents/notes/demo-post/index.md +++ b/drone-plugins/sanitize-links/tmp/blog/contents/notes/drone-and-hugo/index.md @@ -175,7 +175,7 @@ The steps are pretty simple ## Green checkmarks At this point, I've got a fully automated publishing pipeline. As soon as a commit gets pushed to my blog repository, Drone jumps into action and runs a fresh Hugo build. The process is far from perfect, though. -![[Resources/attachments/obsidian-pipeline-screenshot.png]] +![[notes/demo-post/obsidian-pipeline-screenshot.png]] ![[notes/drone-and-hugo/obsidian-pipeline-screenshot.png]]