Pull Request Badge is a GitHub App whose core function is to trigger via GitHub webhooks when a Pull Request is opened or edited, then automatically insert matching badges at the top of the PR description based on the .github/pr-badge.yml configuration in the repository. It was originally built to generate JIRA badges, and later expanded into a more general PR context display tool—for example, linking to preview environments, flagging large PRs, showing ticket numbers, and more.
Its configuration model is lightweight, supporting fields such as label, message, url, color, icon, and imageUrl; badges can link to any URL. The when field allows conditional logic using JavaScript expressions, with access to variables such as PR number, branch name, author, draft status, lines added/deleted, commit count, changed file count, repository name, and more. The site also provides a Playground for building configurations online, helping avoid repeated PR test cycles. In terms of integration, it is tightly coupled with GitHub Apps and the GitHub Pull Request workflow, explicitly supports JIRA badges, and includes many built-in icons for common development tools.
The security explanation is relatively clear: the service connects via GitHub Apps, does not store credentials, does not read code, only reads the .github/pr-badge.yml configuration file, and requests metadata read plus PR read/write permissions. Pricing has two tiers: Free and Pro. The free tier supports public repositories and the web configuration generator; Pro costs USD 85/year plus local taxes, and includes JIRA badges, unlimited badges, unlimited private repositories, and email support. The documentation covers how it works, installation, naming conventions, permissions, fields, and variables—enough for basic onboarding—but there is no apparent information on self-hosting, public APIs/SDKs, SLA, or enterprise management capabilities.
Its strengths are that it fits naturally into GitHub-native workflows, offers decent configuration expressiveness, explains permission boundaries clearly, and charges a fixed annual fee rather than per user. Downsides include its clear limitation to GitHub, the need for a paid plan for private repositories and JIRA support, a lack of self-hosting and API information, and support channels that are mainly email-based. It is well suited to open-source maintainers, small engineering teams, and JIRA-dependent development organizations that collaborate through GitHub PRs and want a standardized way to display PR context.
The main content does not provide details about access from mainland China, network nodes, or payment methods; payment only mentions GitHub Marketplace terms. If a team’s access to GitHub is unstable from within China, the user experience may be affected by GitHub connectivity. Alternatives to consider include custom GitHub Actions scripts, Danger JS, Mergify, or Reviewdog—more general-purpose PR automation tools.
⚠ This review is compiled from public sources and does not constitute a purchase recommendation. Verify all facts on the vendor's official site. Verify on pullrequestbadge.com official site.
pullrequestbadge.com is an Unknown Dev Tools (Github App) provider. TG4G tracks its product information, an overall rating of 6.0/10, and a China-accessibility score of Workable. Click "Visit Official Site" to reach pullrequestbadge.com directly.