summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorelajkat <lajos.katona@est.tech>2020-03-23 13:42:27 +0100
committerLajos Katona <katonalala@gmail.com>2020-03-23 15:04:50 +0000
commit1198962c6001b6d88ab60aa7534e608b91f90465 (patch)
treeb920c8920876915bfddbf442b81f8aa06421aa6d
parentb7312a98807c57bec2cd4f8d0801ff6ab3109e18 (diff)
downloadhorizon-1198962c6001b6d88ab60aa7534e608b91f90465.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. 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 ac94b58c8..bf82d8277 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"