03768832c4
The feature to configure branch names based on the presence of "bug", "lp", "blueprint" or "bp" in the commit message is overly elaborate and very OpenStack specific. Even with this, it hasn't been updated to keep up with the times as many projects have migrated to Storyboard, which isn't handled here. Given that it frequently does the wrong thing and likely doesn't apply to anyone outside of the OpenStack ecosystem, the wisest thing it to simply remove the feature. This is a break in behavior but it seems better than adding yet another flag for something that many users will want enabled by default. Change-Id: I82ecc1719de5c87d59bbfe73a042917e6559da1e Signed-off-by: Stephen Finucane <stephenfin@redhat.com> Story: 1130330 Task: 566 Story: 2001247 Task: 5777
11 lines
525 B
YAML
11 lines
525 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
Support for auto-configuration of topic names based on the presence of
|
|
keywords in the commit message is removed. Previously, keywords such as
|
|
``bug``, ``bp`` or ``lp`` followed by a number would result in branch
|
|
names containing the associated number, e.g. ``bug/123``. This feature
|
|
was OpenStack specific, was a frequent source of bugs and clearly wasn't
|
|
being used that often, given that StoryBoard is a thing now and no one had
|
|
updated this feature to handle that metadata.
|