Browse Source

Tell reno to ignore the kilo branch

This patch was adopted from Idd56c3f37d5786daae7181c36d38d267cbf1885c

Original description:
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: I28fd0fd499c40e33ff164fd643dadd6ac9009b17
Co-Authored-By: Doug Hellmann <doug@doughellmann.com>
Co-Authored-By: Sean McGinnis <sean.mcginnis@gmail.com>
changes/13/709213/2
Kristi Nikolla 1 year ago
parent
commit
175cb0b642
2 changed files with 6 additions and 0 deletions
  1. +2
    -0
      .gitignore
  2. +4
    -0
      reno.yaml

+ 2
- 0
.gitignore View File

@ -34,6 +34,8 @@ keystone/locale/*/LC_MESSAGES/*.mo
*.db
# Files created by releasenotes build
releasenotes/build
RELEASENOTES.rst
releasenotes/notes/reno.cache
# sample config included in docs
doc/source/_static/keystone.conf.sample
etc/keystone.conf.sample


+ 4
- 0
reno.yaml View File

@ -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"

Loading…
Cancel
Save