Skip to content

Guides FAQ and troubleshooting

Answers to common questions and step-by-step fixes for the most frequent issues.

Typically within 30 seconds of the PR event. Analysis runs asynchronously via a background job queue.

Pullminder only reads the PR diff (added and modified lines), not the full repository source code. Diffs are processed in memory and not stored after analysis completes.

Can I use Pullminder without the GitHub App?

Section titled “Can I use Pullminder without the GitHub App?”

Yes. The CLI runs entirely offline against your local branch diff. Use pullminder check for local analysis without any network access or authentication.

After 100 analyzed PRs, Pullminder stops posting PR comments and setting check statuses. Your historical data remains accessible in the dashboard. Upgrade to Starter or Team to resume analysis.

Can I use Pullminder with GitHub Enterprise Server?

Section titled “Can I use Pullminder with GitHub Enterprise Server?”

The CLI works with any Git repository. The platform (GitHub App + dashboard) currently supports GitHub.com only. GitHub Enterprise Server support is on the roadmap.

Each enabled rule pack runs patterns against the PR diff. Findings are weighted by severity and aggregated using a tiered scoring model. The final score is normalized to 0—100. See How risk scoring works for details.

Can I customize which rules run on my repositories?

Section titled “Can I customize which rules run on my repositories?”

Yes. Enable or disable packs per-organization from the dashboard (Settings > Rule packs) or per-repository using overrides. You can also create custom packs with your own patterns.

Yes. Pullminder analyzes the PR diff regardless of repository structure. Rule packs use file path and language filtering, so patterns only match relevant files.

Collective Memory (Beta) tracks per-file history — revert and hotfix patterns, churn, and recurring findings — and surfaces that context in PR reviews. It is display-only and never changes the risk score. Per-repo opt-in, off by default. See the Collective Memory guide for details.

Can Pullminder block a merge based on past incidents?

Section titled “Can Pullminder block a merge based on past incidents?”

Yes. When red-flagging is enabled, a high-risk change to files with prior incidents can fail the Pullminder check. Tune the strictness with red_flag_fail_threshold, or override an individual PR with the pullminder-risk-ack label. See Risk Red-Flagging.

Does Collective Memory affect the risk score?

Section titled “Does Collective Memory affect the risk score?”

No. Collective Memory is display-only. It adds historical context to the review comment and AI brief but never changes the risk score, policy outcomes, or merge decisions.

File-path metadata and aggregate counts only. No source code, no diff contents, no file contents. Disabling a repo purges its memory immediately. GDPR erasure is supported.

  1. Check that the repository is active in the dashboard (Settings > Repositories)
  2. Verify the GitHub App is installed on the repository (GitHub > Settings > Integrations)
  3. If you just installed the app, sign out and back in to sync your organizations
  4. Check that your trial or subscription is active (Settings > Billing)

My organization does not appear in the dashboard

Section titled “My organization does not appear in the dashboard”

Sign out of the dashboard and sign back in. Organization membership is synced from GitHub during login.

Adjust pack weights and enabled packs in Settings > Rule packs. Each pack has a max_weight cap that limits its contribution. Disable packs that produce noisy findings for your codebase.

  1. Ensure you have uncommitted changes or a branch diff against main
  2. Run pullminder check --base <branch> if your base branch is not main
  3. Check that rule packs are configured: run pullminder packs list --enabled
  1. Open Settings > Slack integration and click Test webhook
  2. Verify the webhook URL is correct and the Slack app is still active
  3. Check that notification preferences are enabled for the event type