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:16 +0000
commite6eb4990c82567848fb368493e2565155999e21f (patch)
treeedeb79517444a488e8194e6d0299395952aa77b2
parente058e381607e93439a59f47c36e6a9b7cf61cc71 (diff)
downloadhorizon-e6eb4990c82567848fb368493e2565155999e21f.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"