4.3 KiB
Updating from v2 to v3
Breaking changes
-
The
authorinput now defaults to the user who triggered the workflow run. This default is set via action.yml as${{ github.actor }} <${{ github.actor }}@users.noreply.github.com>, wheregithub.actoris the GitHub user account associated with the run. For example,peter-evans <peter-evans@users.noreply.github.com>.The behavior of
v2can be kept by setting theauthorinput as follows.- uses: peter-evans/create-pull-request@v3 with: author: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> -
The
authorandcommitterinputs are no longer cross-used if only one is supplied. Additionally, when neither input is set, theauthorandcommitterare no longer determined from an existing identity set in git config. In both cases, the inputs will fall back to their default set in action.yml. -
Deprecated inputs
projectandproject-columnhave been removed in favour of an additional action step. See Create a project card for details. -
Deprecated output
pr_numberhas been removed in favour ofpull-request-number. -
Input
request-to-parenthas been removed in favour ofpush-to-fork. This greatly simplifies pushing the pull request branch to a fork of the parent repository. See Push pull request branches to a fork for details.e.g.
- uses: actions/checkout@v2 # Make changes to pull request here - uses: peter-evans/create-pull-request@v3 with: token: ${{ secrets.MACHINE_USER_PAT }} push-to-fork: machine-user/fork-of-repository -
Input
branch-suffixhas been removed to simplify the action and make it easier to understand its behaviour. The same functionality can be achieved by modifying thebranchname before the action runs. See the following example. If you were usingbranch-suffixand need help to update tov3, please create an issue.e.g.
- name: Return a 7 character random string uses: actions/github-script@v2 id: random-string with: result-encoding: string script: return Math.random().toString(36).substr(2, 7) - uses: peter-evans/create-pull-request@v3 with: branch: my-branch-${{ steps.random-string.outputs.result }}
New features
-
The action has been converted to Typescript and is much faster than
v2. -
If you run this action in a container,
pythonandpipare no longer required dependencies. See Running in a container for details. -
Inputs
labels,assignees,reviewersandteam-reviewerscan now be newline separated, or comma separated. e.g.labels: | chore dependencies automated
Updating from v1 to v2
Breaking changes
-
v2now expects repositories to be checked out withactions/checkout@v2To use
actions/checkout@v1the following step to checkout the branch is necessary.- uses: actions/checkout@v1 - name: Checkout branch run: git checkout "${GITHUB_REF:11}" -
The two branch naming strategies have been swapped. Fixed branch naming strategy is now the default. i.e.
branch-suffix: noneis now the default and should be removed from configuration if set. -
author-name,author-email,committer-name,committer-emailhave been removed in favour ofauthorandcommitter. They can both be set in the formatDisplay Name <email@address.com>If neither
authororcommitterare set the action will default to making commits as the GitHub Actions bot user.
New features
- Unpushed commits made during the workflow before the action runs will now be considered as changes to be raised in the pull request. See Controlling commits for details.
- New commits made to the pull request base will now be taken into account when pull requests are updated.
- If an updated pull request no longer differs from its base it will automatically be closed and the pull request branch deleted.