Creates a pull request in a GitHub repository, requiring existing `base` and `head` branches; `title` or `issue` must be provided.
baseRequiredstringThe name of the branch you want the changes pulled into. This must be an existing branch on the current (target) repository. You cannot submit a pull request to one repository that requests a merge to a base branch of another repository.
bodystringThe detailed description or contents of the pull request.
headRequiredstringThe name of the branch where your changes are implemented. IMPORTANT: This branch must already exist in the repository (or fork) before calling this action. You must first create the branch and push commits to it (using git or the 'Create a reference' action), then create the PR…
repoRequiredstringThe name of the repository, without the `.git` extension. This name is not case-sensitive.
draftbooleanIndicates whether the pull request should be created as a draft. Draft pull requests cannot be merged until marked as ready for review.
issueintegerThe number of an existing issue in the repository to convert into a pull request. If provided, the issue's title and body may be used for the pull request. Required if `title` is not specified.
ownerRequiredstringThe account owner of the repository. This name is not case-sensitive.
titlestringThe title of the new pull request. Required unless `issue` is specified.
head_repostringThe name of the repository (e.g., 'octocat/Hello-World') where the changes in the pull request were made. This field is required for cross-repository pull requests if both the source and target repositories are owned by the same organization but are different repositories.
maintainer_can_modifybooleanIndicates whether maintainers of the upstream repository can modify the pull request. This is primarily relevant for pull requests originating from forks.
dataRequiredData from the action execution
errorstringError if any occurred during the execution of the action
successfulRequiredbooleanWhether or not the action execution was successful or not
OAuth connection. Risk level 2 of 5.
Free Action