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

@ -88,7 +88,7 @@ not exist, it is created.
| destination-token | a token with write permission on destination-repo | `true` | |
| update | path to the script to update the content of the cascading PR | `true` | |
| prefix | prefix of the branch from which the cascading PR is created on {destination-repo} or {destination-fork-repo} (default to {origin-repo}) | `false` | |
| close-merge | if true the cascading PR will be closed and the branch deleted when the PR is merged | `false` | false |
| close | if true the cascading PR will be closed and the branch deleted when the PR is merged | `false` | false |
| verbose | if true print verbose information | `false` | false |
| debug | if true print debug information | `false` | false |
<!-- action-docs-inputs -->