summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorelajkat <lajos.katona@est.tech>2020-03-23 13:42:27 +0100
committerAkihiro Motoki <amotoki@gmail.com>2020-03-23 13:18:58 +0000
commit571eb23c79c8a231832cd6478447369320c2cac0 (patch)
tree0034aa8528c7de82a67fca5c4a388ef7a4febbe6
parent7acb68b5c2d4d8e355c80bab861c3cd18e799773 (diff)
downloadhorizon-18.1.0.tar.gz
Tell reno to ignore the kilo branch18.1.0
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
-rw-r--r--.gitignore3
-rw-r--r--reno.yaml3
2 files changed, 6 insertions, 0 deletions
diff --git a/.gitignore b/.gitignore
index b5a20a735..c9393d13c 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 000000000..60b0c183d
--- /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: "(.+)(?<!kilo)-eol"