From 571eb23c79c8a231832cd6478447369320c2cac0 Mon Sep 17 00:00:00 2001 From: elajkat Date: Mon, 23 Mar 2020 13:42:27 +0100 Subject: [PATCH] Tell reno to ignore the kilo branch When reno 3.x runs under setuptools, it scans all of the branches it can find, including any that look like they're closed and have an -eol tag. This patch is a copy of one similar in cinder repo: https://review.opendev.org/707495 Change-Id: I50a50f75a1e70ccc183f598099f0e2f0fff8985a --- .gitignore | 3 +++ reno.yaml | 3 +++ 2 files changed, 6 insertions(+) create mode 100644 reno.yaml diff --git a/.gitignore b/.gitignore index b5a20a735e..c9393d13cf 100644 --- a/.gitignore +++ b/.gitignore @@ -16,8 +16,11 @@ coverage-karma pep8.txt pylint.txt # Files created by releasenotes build +RELEASENOTES.rst releasenotes/build +releasenotes/notes/reno.cache reports + openstack_dashboard/local/* !openstack_dashboard/local/local_settings.py.example !openstack_dashboard/local/enabled/_50__settings.py.example diff --git a/reno.yaml b/reno.yaml new file mode 100644 index 0000000000..60b0c183d5 --- /dev/null +++ b/reno.yaml @@ -0,0 +1,3 @@ +--- +# Ignore the kilo-eol tag because that branch does not work with reno. +closed_branch_tag_re: "(.+)(?