aboutsummaryrefslogtreecommitdiffhomepage
path: root/gbp.conf
diff options
context:
space:
mode:
authorJonathan Toppins <jtoppins@cumulusnetworks.com>2015-08-27 10:09:37 -0400
committerGuido Günther <agx@sigxcpu.org>2015-08-27 19:40:35 +0200
commitc89c29d3584d8e6e4a25eb434849f93b14897485 (patch)
tree8048290a7fcd15b5903c2edafcb49914265c5bdf /gbp.conf
parent488ba325db7d467d813c4966354676e1f943988d (diff)
gbp-dch: allow bug number format to be overridden
Some derivatives and non Debian exclusive projects don't use just numbers for their bug numbers. gbp-dch should still be able to parse these bug numbers and generate useful changelog entries. This doesn't solve dpkg-parsechangelog but is a start. Examples of non-Debian bug numbers are: example change header Example: EX-12345 Should produce the following change log: * example change header (Example: EX-12345) This also helps in pulling CVE numbers simply by letting the user modify the regex to something like 'cve-\d+-\d+'. Signed-off-by: Jonathan Toppins <jtoppins@cumulusnetworks.com> Signed-off-by: Guido Günther <agx@sigxcpu.org>
Diffstat (limited to 'gbp.conf')
-rw-r--r--gbp.conf2
1 files changed, 2 insertions, 0 deletions
diff --git a/gbp.conf b/gbp.conf
index 43fc36dd..64cd3a1e 100644
--- a/gbp.conf
+++ b/gbp.conf
@@ -96,6 +96,8 @@
#meta = False
# what tags to look for to generate bug-closing changelog entries:
#meta-closes = Closes|LP
+# what regex should be used to parse the bug number
+#meta-closes-bugnum = '(?:bug|issue)?\#?\s?\d+'
# include the full commit message in the changelog:
#full = True
# ignore Signed-off-by: lines: