Skip to content

Dashboard settings

The settings page in the Pullminder dashboard lets you configure how Pullminder operates within your organization. Access it from the gear icon in the sidebar at app.pullminder.com.

View and update your organization name and other metadata. The organization is linked to your GitHub organization and is created automatically during onboarding.

Manage which repositories Pullminder monitors and how it interacts with them.

Toggle active — Enable or disable analysis for individual repositories. Disabled repositories still appear in the list but Pullminder will not process their webhooks.

Coverage artifacts — Configure where Pullminder should look for code coverage data. When coverage artifacts are present, Pullminder includes coverage delta information in PR analysis and the reviewer brief.

Badges — Generate a status badge for any repository. The badge displays the latest risk score and can be embedded in your README or documentation. You can create, view, and delete badges per repository.

Framework detection — Pullminder automatically detects the languages and frameworks used in each repository. Based on detected frameworks, it can recommend relevant rule packs. You can enable or disable auto-detected rule packs from this section.

Trigger a baseline scan to analyze recently merged pull requests across your repositories. This establishes a risk profile for your organization and helps identify systemic patterns before you start monitoring new PRs.

The baseline scan runs in the background. You can check its progress from the settings page, and view results in the Reports section once complete.

Connect Pullminder to a Slack channel to receive alerts for high-risk PRs and policy blocks.

  1. Enter your Slack incoming webhook URL in the Slack integration section.
  2. Click Test webhook to send a test message and verify the connection.
  3. Save your settings.

Once configured, Pullminder sends a Slack message whenever a high-risk or policy-blocked PR is detected. The message includes the PR title, repository, risk score, and a link to the PR detail in the dashboard.

Control which events trigger notifications:

PreferenceDescription
High-risk alertsNotify when a PR exceeds the risk threshold
Critical findingsNotify when a finding with critical severity is detected
Policy blocksNotify when a rule with the block action prevents merging

Notifications appear in the dashboard alerts page and, if configured, are also sent to Slack.

By default, Pullminder loads rule packs from the official registry. If your team maintains a private registry, you can configure it here.

  • Add a registry — Enter the URL of your custom registry endpoint. Pullminder will fetch available rule packs from this source.
  • Sync — Manually trigger a sync to pull the latest rule packs from your custom registry.
  • Remove — Delete the custom registry and revert to the official registry only.

Configure how long Pullminder retains analysis data. Retention policies can be set per resource type (PR analyses, findings, audit logs). Shorter retention periods reduce stored data; longer periods preserve historical context for analytics.

Toggle whether Pullminder generates the AI-powered reviewer brief on each PR. When enabled, the analysis comment includes a narrative summary of what changed and where to focus. When disabled, Pullminder posts only the risk score and findings list.

Actions in the danger zone are destructive and cannot be undone.

Delete organization — Permanently removes the organization, all repositories, analysis history, rules, and settings from Pullminder. This does not affect your GitHub organization or repositories. You will be asked to confirm before deletion proceeds.