Skip to main content
Click the Settings icon on the dashboard to customize how Gitar operates across your organization. Each section below corresponds to a configuration panel in the settings page.

​
Agent UX

Control the default auto-fix behavior for CI failures across all PRs/MRs. You can choose between opt-in mode, where authors must explicitly request fixes, and opt-out mode, where Gitar automatically attempts to fix CI failures unless disabled on a per-PR/MR basis. This is particularly useful during initial rollout so your team can get comfortable with the agent before enabling it organization-wide.

​
AI Rules

Provide organization-wide instructions that guide the Gitar agent across all connected repositories. These rules let you enforce coding standards, preferred libraries, or architectural patterns at the org level. Gitar also automatically picks up repo-level rule files such as AGENTS.md, CLAUDE.md, and .cursorrules — see Customize for details.

​
Code Review

Enable or disable automatic code reviews for all incoming PRs/MRs. When enabled, Gitar will review every PR/MR and post a summary with actionable feedback. You can configure a merge blocking threshold to control how Gitar’s review verdict affects mergeability. The available levels are Approved, Approved with Suggestions, Changes Requested, and Blocked.

​
GitHub Status Checks

Toggle whether Gitar displays a status check indicator on GitHub PRs while it is processing. Disabling this setting reduces visual noise in the Checks tab, which can be helpful for teams with many CI integrations.

​
PR Summary

Enable or disable automatic PR summary generation. When active, Gitar produces a concise summary of the changes in every PR/MR. This setting is enabled by default and can also be configured during initial onboarding.

​
Bot Allowlist

Configure which bot accounts Gitar should process. By default, all bot-authored changes are skipped to avoid unnecessary noise. If you want Gitar to review or act on changes from specific bots (e.g., Dependabot, Renovate), add them to the allowlist here.

​
Filters

Control which users’ PRs/MRs Gitar processes by specifying a comma-separated list of allowed authors. Leave the field empty to process PRs/MRs from all users. This is useful for gradual rollouts, team-based access control, or testing Gitar with a subset of contributors before wider deployment. You can also filter PRs/MRs by label on a per-repository basis. When label filtering is configured, Gitar will only process PRs/MRs that carry the specified labels, giving you fine-grained control over which changes receive automated attention.