From 20ac681e9eeec998e5a394dd230ea2dfdc457f82 Mon Sep 17 00:00:00 2001
From: Marco Pivetta <ocramius@gmail.com>
Date: Tue, 28 Jul 2020 18:04:17 +0200
Subject: [PATCH] #11 clarifying merge-up PR scenario description

Ref: https://github.com/laminas/automatic-releases/pull/12#discussion_r461142193
---
 feature/automated-releases.feature | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/feature/automated-releases.feature b/feature/automated-releases.feature
index 3aee137d..5923fe8a 100644
--- a/feature/automated-releases.feature
+++ b/feature/automated-releases.feature
@@ -51,7 +51,9 @@ Feature: Automated releases
     When I close milestone "1.1.0"
     Then the tool should have halted with an error
 
-  Scenario: If a minor release branch exists, the tool creates a new minor release from there
+  Scenario: If a minor release branch exists, when closing the minor release milestone,
+  the tool tags the minor release from the branch, and creates a pull request
+  against the next newer minor release branch.
     Given following existing branches:
       | name   |
       | 1.1.x  |