A GitHub Action that automatically creates or updates pull requests from changes made during a workflow run.
Create Pull Request is a GitHub Action that automatically creates or updates pull requests from changes generated during a GitHub Actions workflow execution. It solves the problem of manually creating PRs for automated code changes, such as dependency updates, generated documentation, or CI-driven modifications, by detecting workspace changes and handling the entire PR lifecycle.
Developers and DevOps engineers who use GitHub Actions for CI/CD and need to automate the creation of pull requests from workflow-generated changes, such as automated updates, code generation, or bot contributions.
Developers choose this action for its robustness, extensive configuration options, and seamless integration with GitHub's ecosystem, eliminating manual PR creation steps and ensuring consistent, automated code review workflows.
A GitHub action to create a pull request for changes to your repository in the actions workspace
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Detects untracked, modified, and uncommitted changes in the workspace automatically, eliminating the need for manual git staging and commit commands.
Supports fixed branch names for ongoing updates or unique suffixes like random or timestamp for new branches each run, with configurable strategies.
Offers inputs for commit messages, labels, assignees, reviewers, draft PRs, and more, allowing precise control over PR metadata and behavior.
Works with GITHUB_TOKEN, PATs, or GitHub App tokens, with detailed guidance on scopes and permissions to suit different automation needs.
Using the default GITHUB_TOKEN prevents triggering subsequent workflow runs on push or pull_request events, forcing use of alternative tokens for full automation cycles.
The delete-branch feature does not delete branches immediately upon merge, requiring the action to run again to clean up, which can leave stale branches in the repository.
Managing different tokens for branch and PR operations or configuring pathspecs for file inclusion adds complexity, especially for edge cases like proxy support or fork workflows.