Behaviour changes
- The action will no longer leave the local repository checked out on the pull request
branch
. Instead, it will leave the repository checked out on the branch or commit that it was when the action started. - When using
add-paths
, uncommitted changes will no longer be destroyed. They will be stashed and restored at the end of the action run.
What's new
- Adds input
body-path
, the path to a file containing the pull request body. - At the end of the action run the local repository is now checked out on the branch or commit that it was when the action started.
- Any uncommitted tracked or untracked changes are now stashed and restored at the end of the action run. Currently, this can only occur when using the
add-paths
input, which allows for changes to not be committed. Previously, any uncommitted changes would be destroyed. - The proxy implementation has been revised but is not expected to have any change in behaviour. It continues to support the standard environment variables
http_proxy
,https_proxy
andno_proxy
. - Now sets the git
safe.directory
configuration for the local repository path. The configuration is removed when the action completes. Fixes issue #1170. - Now determines the git directory path using the
git rev-parse --git-dir
command. This allows users with custom repository configurations to use the action. - Improved handling of the
team-reviewers
input and associated errors.
News
🏆 create-pull-request won an award for "awesome action" at the Open Source Awards at GitHub Universe. Thank you for your support and for making create-pull-request one of the top used actions. Please give it a ⭐, or even buy me a coffee.
What's Changed
- v5 by @peter-evans in #1792
- 15 dependency updates by @dependabot
Full Changelog: v4.2.4...v5.0.0