From f1118505536fed316ac3d4e882c2ef9e1dc3818d Mon Sep 17 00:00:00 2001 From: Sean Whitton Date: Tue, 17 Mar 2020 11:32:10 -0700 Subject: don't continue if fail to push the gitforge branch Signed-off-by: Sean Whitton --- Changes | 2 ++ lib/API/GitForge/Role/GitForge.pm | 3 ++- 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/Changes b/Changes index f678f79..fd4b038 100644 --- a/Changes +++ b/Changes @@ -1,6 +1,8 @@ Revision history for API::GitForge {{$NEXT}} + - API::GitForge::Role::GitForge::clean_repo(): don't continue if + fail to push the gitforge branch. 0.004 2020-03-13 17:28:05-07:00 America/Phoenix - API::GitForge::Role::GitForge::clean_repo(): reinstate diff --git a/lib/API/GitForge/Role/GitForge.pm b/lib/API/GitForge/Role/GitForge.pm index 953eb91..1301f88 100644 --- a/lib/API/GitForge/Role/GitForge.pm +++ b/lib/API/GitForge/Role/GitForge.pm @@ -126,7 +126,8 @@ sub clean_fork { # but that hangs indefinitely when pushing to (at least) Debian's # GitLab instance. So just bypass Git::Wrapper and do the push # ourselves for now - system qw(git -C), $git->dir, "push", $fork_uri, "master:gitforge"; + system qw(git -C), $git->dir, "push", $fork_uri, "master:gitforge" + or croak "failed to push the gitforge branch to $fork_uri"; $self->_clean_config_fork($_[0]); -- cgit v1.2.3