From fe9ac6a286fe44afed3248e7e5db0444f3969996 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?El=C5=91d=20Ill=C3=A9s?= Date: Tue, 8 Jul 2025 15:48:03 +0200 Subject: [PATCH] [release-tools] Improve tagging logs When EOL-tagging cycle-trailing projects when a series is already EOL, the tagging is still processed, but branching has to be skipped. During the refactor the same log message was used, hence during debugging it cannot be determined when we returned. This patch rephrases the log message to be unique. Change-Id: Id4645f9661d485e3e1aa7069fb0b279659d2f7f0 --- .../files/release-tools/process_release_requests.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/copy-release-tools-scripts/files/release-tools/process_release_requests.py b/roles/copy-release-tools-scripts/files/release-tools/process_release_requests.py index af08631866..99d84b80d3 100755 --- a/roles/copy-release-tools-scripts/files/release-tools/process_release_requests.py +++ b/roles/copy-release-tools-scripts/files/release-tools/process_release_requests.py @@ -229,7 +229,7 @@ def process_release_requests(reporoot, filenames, meta_data): # If the series is closed, do not process the branch # section to avoid already deleted branch re-creation. if closed_series: - print(' {} skipping closed series'.format(filename)) + print(' {} skipping branching, closed series'.format(filename)) continue # Create branches and adapt master