PullPro
PullPro posts each GitHub pull request to the right Slack channel once its checks pass, lets a reviewer claim it in one click, and nudges until it merges.Pull requests on GitHub — proposed code changes that a teammate reviews before they're merged — tend to stall when nobody notices them or knows who's picking them up. PullPro brings them into the Slack channels your team already uses, so every pull request has a clear reviewer and keeps moving.How it works
• Posted when it's ready — PullPro waits for your required checks to pass, then posts the pull request to the channels it routes to, tagging the author. Check status, claims and approvals update the same message as reactions, so the channel stays quiet.
• Claim reviews explicitly — reviewers click Claim review to take a pull request, so it's always clear who's responsible.
• Reminders on your schedule — unclaimed pull requests get reminders in the channel during the working hours you set, until someone claims them.
• Direct messages for the right person — reviewers hear when they're asked to review or mentioned on GitHub; authors hear when checks fail (with a Post now button), when there's a merge conflict, or when an approved pull request is still unmerged.
• Routing per channel — include pull requests by reviewer team, author's team, repository, label or target branch, or simply all of them. Exclude labels such as Dependabot's
• Review metrics — a weekly report in the channel covers time to first review and how many merges got a human review, and
• Move and post on demand — move a pull request to another channel from its message, or post one by hand with
When a coding agent or bot opens a pull request, PullPro credits the person it's assigned to: they're the one notified, it routes by their team, and it counts in their numbers.Getting started
1. Add PullPro to your Slack workspace.
2. From PullPro's App Home, connect your GitHub organization.
3. Link a channel and choose which pull requests it receives.PullPro reads pull request metadata such as titles, reviewers and check results. It never reads file contents or diffs.
• Posted when it's ready — PullPro waits for your required checks to pass, then posts the pull request to the channels it routes to, tagging the author. Check status, claims and approvals update the same message as reactions, so the channel stays quiet.
• Claim reviews explicitly — reviewers click Claim review to take a pull request, so it's always clear who's responsible.
• Reminders on your schedule — unclaimed pull requests get reminders in the channel during the working hours you set, until someone claims them.
• Direct messages for the right person — reviewers hear when they're asked to review or mentioned on GitHub; authors hear when checks fail (with a Post now button), when there's a merge conflict, or when an approved pull request is still unmerged.
• Routing per channel — include pull requests by reviewer team, author's team, repository, label or target branch, or simply all of them. Exclude labels such as Dependabot's
dependencies or bot authors, and hold labelled pull requests until they merge with Post when merged.• Review metrics — a weekly report in the channel covers time to first review and how many merges got a human review, and
/pullpro stats shows your own numbers, visible only to you.• Move and post on demand — move a pull request to another channel from its message, or post one by hand with
/pullpro.Built for how teams work todayWhen a coding agent or bot opens a pull request, PullPro credits the person it's assigned to: they're the one notified, it routes by their team, and it counts in their numbers.Getting started
1. Add PullPro to your Slack workspace.
2. From PullPro's App Home, connect your GitHub organization.
3. Link a channel and choose which pull requests it receives.PullPro reads pull request metadata such as titles, reviewers and check results. It never reads file contents or diffs.
PullPro will be able to view:
PullPro will be able to do:
Review the details to better understand this app’s security practices. To learn more about assessing apps for your workspace visit our Help Center.
General
Developer
Michael Herrmann
Company headquarters location
Canada
Terms of service
Privacy & data governance
Data retention policy
PullPro retains Customer Data only while the app is installed and in use. Pull request metadata (titles, status, reviewers, timestamps) is kept while the workspace is connected so review metrics can cover past periods. PullPro never stores source code, file contents, diffs or Slack message content. Application logs and error logs are kept for 30 days.
Data archiving and removal policy
When PullPro is uninstalled from a Slack workspace, that workspace's data is marked for deletion immediately and permanently erased 14 days later; reinstalling within those 14 days restores it. Customers can also request deletion at any time by emailing support@pullpro.dev. PullPro does not archive Customer Data.
Data storage policy
Customer Data is stored in a managed PostgreSQL database in the United States, encrypted in transit and at rest, and accessible only to PullPro's operators on a need-to-know basis. Short-lived caches (minutes to days) run on Cloudflare's global network.
Data center location(s)
United States
Data hosting details
Cloud hosted: the application runs on Cloudflare Workers and the data is stored in a managed Prisma Postgres database.
Data hosting company
Cloudflare, Prisma
App/service has sub-processors
yes
Guidelines for sub-processors
App/service uses large language models (LLM)
no
Certifications & compliance
Data deletion request procedure
Workspace data. Uninstalling PullPro from Slack starts deletion automatically: the workspace's data is marked for deletion immediately and permanently erased 14 days later by a daily purge job. Reinstalling within that window restores it and cancels the scheduled deletion.
Requests by email. A workspace user can request deletion at support@pullpro.dev. We then schedule the workspace for the same purge, so its data is erased within 14 days. We confirm by email once it's done.
Individual users. A user can ask support@pullpro.dev to delete the data linked to their Slack or GitHub account. We remove it within 14 days and confirm by email.
Application logs and error reports are not deleted individually; they expire on their own after 7 and 30 days.
HIPAA compliant
no
While this app may offer HIPAA compliance, Slack does not have a business associate agreement with any third-party application providers, including those in the Slack Marketplace, so you are responsible for validating the provider's compliance and executing an appropriate agreement before enabling.
Security
Supports Security Assertion Markup Language (SAML)
no
Has a dedicated security team
no
Contact for security issues
support@pullpro.dev
Has a vulnerability disclosure program
no
Has a bug bounty program
no
Requires third party authorization/connections
yes
Third party services used by this app
GitHub (GitHub App and OAuth, the source of pull request data), Cloudflare (hosting and caching), Prisma (managed PostgreSQL database), Sentry (error reporting), Mixpanel (product analytics)
Uses token rotation
no