close-merge is close and applies to destination-ref as well

* workflows that have close-merge need to change to close
* the behavior for when origin-pr is set does not change
* the behavior for when origin-ref is set is to honor close
  instead of always closing the PR
This commit is contained in:
Earl Warren 2024-01-09 19:47:48 +01:00
parent 5007c13756
commit 09dc15f425
No known key found for this signature in database
GPG key ID: 0579CB2928A78A00
5 changed files with 14 additions and 10 deletions

View file

@ -103,8 +103,8 @@ inputs:
required: true
prefix:
description: 'prefix of the branch from which the cascading PR is created on {destination-repo} or {destination-fork-repo} (default to {origin-repo})'
close-merge:
description: 'if true the cascading PR will be closed and the branch deleted when the PR is merged'
close:
description: 'if true the cascading PR will be closed and the branch deleted when (i) the {origin-pr} is merged or (ii) when the cascading PR status is success if {origin-ref} is set'
default: false
verbose:
description: 'if true print verbose information'
@ -145,5 +145,5 @@ runs:
--destination-branch "${{ inputs.destination-branch }}" \
--update "${{ inputs.update }}" \
--prefix "${{ inputs.prefix }}" \
--close-merge "${{ inputs.close-merge }}" \
--close "${{ inputs.close }}" \
run