diff options
| author | Pierre Riteau <pierre@stackhpc.com> | 2020-02-12 17:28:44 +0100 |
|---|---|---|
| committer | Pierre Riteau <pierre@stackhpc.com> | 2020-02-12 17:28:44 +0100 |
| commit | 8770b9223005a52c5270556606be43909895b9f3 (patch) | |
| tree | 06458fc5d6c95b8a689ba8457468138c1730f483 /reno.yaml | |
| parent | f19037c1b616f2ecb8fd4a1d446687538327e687 (diff) | |
| download | ceilometer-8770b9223005a52c5270556606be43909895b9f3.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.
Change-Id: I8047d805b0a3da4051a6d618ed9ac40875b8636a
Co-Authored-By: Doug Hellmann <doug@doughellmann.com>
Story: 2007274
Task: 38749
Diffstat (limited to 'reno.yaml')
| -rw-r--r-- | reno.yaml | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/reno.yaml b/reno.yaml new file mode 100644 index 00000000..dd0aac79 --- /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" |