From 4e91fa56d12866f81b820244f9125c2da4fa762a Mon Sep 17 00:00:00 2001 From: Pierre Riteau Date: Wed, 12 Feb 2020 17:28:44 +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. 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. Change-Id: I8047d805b0a3da4051a6d618ed9ac40875b8636a Co-Authored-By: Doug Hellmann Story: 2007274 Task: 38749 (cherry picked from commit 8770b9223005a52c5270556606be43909895b9f3) --- reno.yaml | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 reno.yaml diff --git a/reno.yaml b/reno.yaml new file mode 100644 index 0000000000..dd0aac790b --- /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: "(.+)(?