yykamei/Merge Branches Managed on Issue

This actions is responsible for merging listed branches on the specified GitHub issue.

Trust Signals

name	description	required	default
issue-number	The GitHub issue number in which the branches are listed	yes	—
path	Relative path under $GITHUB_WORKSPACE to place the repository	no	—
shell	The shell command to invoke a specified source code. This is typically used for `before-merge` option. The default is `bash -eo pipefail` on Linux. Currently, the Windows platform is not supported. Note this value will be just splitted by whitespaces	no	—
before-merge	Script that will be run before merging through the `shell` option. This will be invoked after checking out to each target and the base branch, so you can modify commits for each branch. This is useful to avoid possible merge conflicts	no	—
after-merge	Script that will be run after merging through the `shell` option. This will be invoked after checking out to each target and the base branch, so you can modify commits for each branch	no	—
inputs-param-base-branch	The name for a base branch in the workflow_dispatch action. The default is "base-branch"	no	—
inputs-param-force	The name for force option in the workflow_dispatch action. The default is "force"	no	—
modified-branch-suffix	The suffix for the modified branch. If you don't set `before-merge` or `after-merge`, the modified branch and the original branch will be the same. The default is ".modified"	no	—
comment-prefix	The comment prefix to trigger some actions. The default is "/mbmi".	no	—
token	The GitHub token used to create an authenticated client	no	${{ github.token }}

name	description
diff	The output of git-diff(1) between the default branch and the head of the merged branch.
diffstat	The output of git-diff(1) with `--stat` between the default branch and the head of the merged branch.