This is an automated email from the ASF dual-hosted git repository.
royteeuwen pushed a change to branch feature/SLING-13253-promote-drop
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-committer-cli.git
omit 8f3503f SLING-13253 - release promote and drop staging repository
commands
add 7089065 SLING-13253 - close-staging: cover interactive-no,
description fallback and error paths
add 71571fa SLING-13253 - release promote and drop staging repository
commands
add 1dd4286 SLING-13253 - promote/drop: extract shared execution-mode
handling
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (8f3503f)
\
N -- N -- N refs/heads/feature/SLING-13253-promote-drop (1dd4286)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.../apache/sling/cli/impl/release/DropCommand.java | 43 +++--------
.../sling/cli/impl/release/PromoteCommand.java | 63 ++++++++--------
.../cli/impl/release/StagingCommandSupport.java | 85 ++++++++++++++++++++++
.../cli/impl/release/CloseStagingCommandTest.java | 29 ++++++++
4 files changed, 156 insertions(+), 64 deletions(-)
create mode 100644
src/main/java/org/apache/sling/cli/impl/release/StagingCommandSupport.java
