A GitHub Action that automatically labels pull requests based on branch name patterns like feature/* or fix/*.
PR Labeler is a GitHub Action that automatically applies labels to pull requests based on the naming patterns of their source branches. It solves the problem of manual labeling by automating the process, ensuring consistency and saving time for development teams. The tool integrates with GitHub's workflow system to trigger on PR openings and can be configured with custom rules.
Development teams and open-source maintainers who use GitHub for version control and want to automate their pull request management and labeling workflows.
Developers choose PR Labeler for its simplicity, zero-configuration defaults, and seamless integration with GitHub Actions. It reduces manual effort, enforces labeling consistency, and works well alongside other automation tools like Release Drafter.
Automatically labels your PRs based on branch name patterns like feature/* or fix/*.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Triggers on PR openings to apply labels based on branch patterns, reducing manual effort as shown in the default workflow that uses on: pull_request types: [opened].
Supports custom YAML configuration with wildcard matching, allowing teams to define their own branch-to-label mappings, evidenced by the example .github/pr-labeler.yml file in the README.
Works directly within GitHub Actions workflows with minimal setup, requiring only read and write permissions for pull requests, and integrates with tools like Release Drafter for changelog generation.
Includes sensible default mappings for common patterns like feature/* and fix/*, making it usable immediately without configuration, as specified in the README.
Automatically created labels have no color or description and aren't permanently saved to the repository's labels page, as admitted in the README, which hinders visual organization and long-term management.
Relies solely on branch naming conventions, ignoring PR titles, descriptions, or file changes, which may not capture nuanced labeling needs like bug severity or feature scope.
Only supports wildcard matching via the matcher library, lacking regex or advanced logic, which could limit complex use cases such as conditional labeling based on multiple criteria.