summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDoug Hellmann <doug@doughellmann.com>2020-02-07 16:37:59 -0500
committerMark Goddard <mark@stackhpc.com>2020-02-10 10:36:13 +0000
commitfa9b8be9956615de4428b02b324a21deeabb2cf0 (patch)
treeeccde2354dab8ad5a9642b1fcafdc374fa8d5c6f
parent6ceec86ad4082390b7226ca66d524b562e74101b (diff)
downloadironic-fa9b8be9956615de4428b02b324a21deeabb2cf0.tar.gz
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. The old kilo branch in this repository has a jumbled history that somehow makes it look like it should include tags that it doesn't. We know that there are no release notes in that branch, because reno wasn't adopted while it was open. The releasenotes/source/index.rst links to separate release notes in the wiki. This patch tells reno to ignore that branch so that it doesn't throw an exception when it gets confused about the old tag. Story: #2007274 Task: #38710 Change-Id: I8047d805b0a3da4051a6d618ed9ac40875b8636a Signed-off-by: Doug Hellmann <doug@doughellmann.com> (cherry picked from commit 0f4b9e38a2924a693e17d815b16f19223f16632a)
-rw-r--r--reno.yaml4
1 files changed, 4 insertions, 0 deletions
diff --git a/reno.yaml b/reno.yaml
new file mode 100644
index 000000000..dd0aac790
--- /dev/null
+++ b/reno.yaml
@@ -0,0 +1,4 @@
+---
+# Ignore the kilo-eol tag because that branch does not work with reno
+# and contains no release notes.
+closed_branch_tag_re: "(.+)(?<!kilo)-eol"