From 7db9a4a288e598ce66344675dc67f3638bb66ddc Mon Sep 17 00:00:00 2001 From: Jay Faulkner Date: Thu, 26 Jan 2023 15:36:14 -0800 Subject: [PATCH] Move and fix reno config for releasenotes job In its current place, reno config changes will not cause build-openstack-releasenotes job to run, which means changes can land to that config without being tested. Yikes! Also fixes error in regexp which was preventing this from actually fixing the build-openstack-releasenotes job. Co-Authored-By: Adam McArthur Change-Id: I4d46ba06ada1afb5fd1c63db5850a1983e502a6c (cherry picked from commit fbe22b23bc3f1c89822e17417747378c9449ebeb) --- releasenotes/config.yaml | 5 +++++ reno.yaml | 4 ---- 2 files changed, 5 insertions(+), 4 deletions(-) create mode 100644 releasenotes/config.yaml delete mode 100644 reno.yaml diff --git a/releasenotes/config.yaml b/releasenotes/config.yaml new file mode 100644 index 0000000000..26538010e5 --- /dev/null +++ b/releasenotes/config.yaml @@ -0,0 +1,5 @@ +--- +# Ignore the kilo-eol tag because that branch does not work with reno +# and contains no release notes. +# Ignore bugfix tags because their releasenotes are covered under stable +closed_branch_tag_re: 'r"(?!^(kilo-|bugfix-)).+-eol$"' diff --git a/reno.yaml b/reno.yaml deleted file mode 100644 index dd0aac790b..0000000000 --- a/reno.yaml +++ /dev/null @@ -1,4 +0,0 @@ ---- -# Ignore the kilo-eol tag because that branch does not work with reno -# and contains no release notes. -closed_branch_tag_re: "(.+)(?