> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gitar.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Organization Settings

> Customize Gitar's Behavior

export const ThemeImage = ({src, alt}) => {
  let lightSrc, darkSrc;
  if (src.includes("-light.")) {
    lightSrc = src;
    darkSrc = src.replace("-light.", "-dark.");
  } else if (src.includes("-dark.")) {
    darkSrc = src;
    lightSrc = src.replace("-dark.", "-light.");
  } else {
    lightSrc = src;
    darkSrc = src;
  }
  return <span>
      <img className="block dark:hidden rounded-lg border" src={lightSrc} alt={alt} />
      <img className="hidden dark:block rounded-lg border" src={darkSrc} alt={alt} />
    </span>;
};

Click the **Settings** icon on the dashboard to customize how Gitar operates across your organization.

## Configuration Scopes

Settings are configured at two levels:

* **Organization level** — sets the defaults for every repository connected to Gitar.
* **Repository level** — overrides specific org defaults for a single repo.

The org view is where you set defaults for behavior controls such as skip draft PRs, merge blocking, auto-approve, and auto-merge. When a repository needs different behavior, open its overrides dialog from the repository list. The dialog highlights which settings differ from the org default and lets you reset any override in one click.

<Note>
  Repository overrides only change settings that are explicitly toggled. Everything else inherits from the org default.
</Note>

## Behavior

<ThemeImage src="/assets/images/behavior-settings-light.png" alt="Behavior settings" />

### Skip drafts

When enabled, Gitar ignores draft PRs until they are marked ready for review.

### Enhance summaries

When enabled, Gitar auto-fills PR descriptions with a summary of the changes.

### Retry unrelated CI failures

Automatically retry CI jobs whose failures are unrelated to the changes in your PR — for example, flaky tests or transient infrastructure issues. Retries once per commit.

### Block merges

Configure a severity threshold for Gitar's code review verdict. When findings meet or exceed the threshold, Gitar submits a blocking review to prevent merging.

### `gitar unblock`

Enable the **gitar unblock** toggle to allow PR authors to dismiss Gitar's blocking review by commenting `gitar unblock`.

### Auto-approve

Enable **Auto-approve PRs based on code review** to let Gitar submit an approving review when a PR passes code review. You can optionally provide natural-language criteria to restrict which PRs qualify. When no criteria are configured, Gitar approves any PR with no blocking findings.

See [Auto-Approve](/features/code-review/auto-approve) for criteria examples, per-repo config files, and platform behavior.

### `gitar-approved` label

Enable **Apply gitar-approved label** in the auto-approve settings to have Gitar add a `gitar-approved` label to approved PRs. The label is created automatically in the repository if it does not exist, making approved changes easy to filter in your platform's PR list.

### Auto-merge

Enable **Auto-merge PRs after auto-approve** to arm your platform's native auto-merge immediately after Gitar approves. On [GitHub](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request) you can choose the merge method (squash, merge commit, or rebase). On [GitLab](https://docs.gitlab.com/user/project/merge_requests/auto_merge/) the project's default merge method is used.

See [Auto-Merge](/features/code-review/auto-merge) for prerequisites and details.

## Custom Instructions

Provide organization-wide instructions that guide the Gitar agent across all connected repositories. These are applied to every repo in your org. Use them to enforce coding standards, preferred libraries, or architectural patterns. Gitar also picks up repo-level instruction files such as `AGENTS.md`, `CLAUDE.md`, and `.cursorrules` — see [Repository Configuration](/configuration/repository-config) for details.

<ThemeImage src="/assets/images/custom-instructions-light.png" alt="Custom instructions" />

## Scope

Control which PRs Gitar processes. All three fields accept comma-separated usernames.

<ThemeImage src="/assets/images/scope-settings-light.png" alt="Scope settings" />

* **Allowed authors** — Only process PRs from these users. Leave empty to process all users.
* **Excluded authors** — Skip PRs from these users, even if they match the allowed list.
* **Allowed bots** — Bot accounts Gitar should process. By default all bot-authored changes are skipped. Add bots like Dependabot or Renovate here to include them.

### Skipping PRs with `gitar-skip`

Add the `gitar-skip` label to any PR to skip all Gitar processing for that change. This works regardless of other scope settings and is useful for one-off exclusions without changing your org or repo configuration.