From 82498467a526e2170b10b8822a1e098da1914f32 Mon Sep 17 00:00:00 2001 From: kdoroszko-splunk Date: Thu, 5 Sep 2024 15:29:32 +0200 Subject: [PATCH] chore: move runbook picture --- runbooks/backporting-changes-to-older-version.md | 2 +- .../images}/backporting/compare-tags.png | Bin 2 files changed, 1 insertion(+), 1 deletion(-) rename {images => runbooks/images}/backporting/compare-tags.png (100%) diff --git a/runbooks/backporting-changes-to-older-version.md b/runbooks/backporting-changes-to-older-version.md index b6bd8dcf2..622ffa186 100644 --- a/runbooks/backporting-changes-to-older-version.md +++ b/runbooks/backporting-changes-to-older-version.md @@ -42,5 +42,5 @@ This runbook shows a real example of backporting changes correlated to `ta-autom - uncheck `Set as the latest release` box - click `Publish release` - check if the release is available, and it points at the proper version - https://github.com/splunk/addonfactory-workflow-addon-release/tags tag `v4.16` should point to the same commit as tag `v4.16.15` - tags + tags - run the workflow for some TA using v4.16 to verify if the pipeline works as expected. \ No newline at end of file diff --git a/images/backporting/compare-tags.png b/runbooks/images/backporting/compare-tags.png similarity index 100% rename from images/backporting/compare-tags.png rename to runbooks/images/backporting/compare-tags.png