GitAuto Logo
  1. Home
  2. Pricing
  3. Docs
  4. Dashboard
  5. Blog
  6. Contact
  1. Home
  2. How It Works
  3. Use Cases
  4. Pricing
  5. Docs
  6. Dashboard
  7. FAQ
  8. Blog
  9. Contact

Auto-Merge

Automatically merge GitAuto pull requests when all tests pass and conditions are met. Save time by eliminating manual PR merging for test generation tasks.

How Auto-Merge Works

Auto-merge happens immediately when check suite completes successfully and all conditions are met:

  • All status checks pass
  • No merge conflicts
  • Branch is up to date
  • Repository does NOT require reviews (reviews haven't happened yet at this point)

Important:Auto-merge won't work if your repository requires reviews in branch protection. See the configuration section below to learn how to bypass this requirement.

Who Should Use This

Teams with scheduled triggers creating many PRs per day who are already familiar with GitAuto's changes and want to reduce the manual burden of merging PRs they would normally merge without detailed code review when tests pass.

Enabling Auto-Merge

To enable auto-merge for your repository, go to Actions Settings and configure the following:

  1. Select your repository from the dropdown
  2. Toggle "Auto-merge" to enabled
  3. Only test files (optional): Only auto-merge when PR contains exclusively test files
  4. Merge method: Choose merge, squash, or rebase method

Bypassing Branch Protection Approval Requirements

If your repository requires pull request approvals in branch protection (e.g., "Require 2 approving reviews"), you need to configure GitAuto to bypass this requirement while keeping it for human developers.

Configuration Steps

  1. Navigate to your repository on GitHub
  2. Go to Settings → Branches
  3. Under "Branch protection rules", find your default branch (usually main or master) and click Edit
  4. Scroll down to the "Require a pull request before merging" section
  5. Check the box: "Allow specified actors to bypass required pull requests"
  6. In the search field, type git and select gitauto-ai from the dropdown
GitHub branch protection settings showing 'Allow specified actors to bypass required pull requests' checkbox and search field with gitauto-ai selected

Result:

  • Human developers still need approving reviews to merge PRs
  • GitAuto can auto-merge its own PRs without approvals when tests pass
  • All other branch protection rules remain enforced for everyone

Troubleshooting

If GitAuto cannot merge after configuration:

  • Verify GitAuto is installed on the repository
  • Check that auto-merge is enabled in GitAuto Actions Settings
  • Ensure the branch protection rule is applied to the correct branch
  • Confirm all required status checks are passing
  • Make sure there are no merge conflicts
  • Verify the branch is up to date with the base branch

Need Help Configuring Auto-Merge?

Branch protection rules can be tricky to configure correctly. If you're having trouble getting auto-merge to work with your specific setup, we're here to help!

Contact us and we'll help you get auto-merge working.

Repository Rules

Getting Started

  • Installation
  • Setup

Triggers

  • Overview
  • Schedule Trigger
  • Test Failure Trigger
  • Review Comment Trigger
  • Dashboard Trigger

Coverage Dashboard

  • Overview
  • Python Testing
  • JavaScript Testing
  • Java Testing
  • Go Testing
  • PHP Testing
  • Ruby Testing
  • Flutter Testing
  • Multi-Language
  • Coverage Charts

Customization

  • Repository Rules
  • Output Language
  • GITAUTO.md

Integrations

  • CircleCI Integration
  • npm Integration

How It Works

Context Enrichment

  • Line Numbers
  • Full File Reads
  • Test File Preloading
  • Test Naming Detection
  • Error Baselines
  • CI Log Cleaning
  • Trigger-Specific Prompts
  • Coding Standards

Output Auto-Correction

  • Diff Hunk Repair
  • Diff Prefix Repair
  • Tool Name Correction
  • Tool Argument Correction
  • Import Sorting
  • Trailing Space Removal
  • Final Newline
  • Line Ending Preservation
  • Sanitize Tool Arguments
  • Lint Disable Headers

Quality Verification

  • Formatting
  • Linting
  • Type Checking
  • Test Execution
  • Coverage Enforcement
  • phpcs / phpstan Support
  • PHPUnit Support
  • pytest Support
  • Snapshot Auto-Update
  • Untestable Detection
  • Should-Skip Detection
  • Dead Code Removal
  • Quality Check Scoring
  • Quality Checklist

Safety Guardrails

  • File Edit Restrictions
  • Temperature Zero
  • PR/Branch Checks
  • Race Condition Prevention
  • Bot Loop Prevention
  • Webhook Deduplication
  • Duplicate Error Hashing
  • Infrastructure Failure Detection
  • Strict Tool Schemas
  • No-Change Detection

Token/Cost Management

  • Token Trimming
  • Outdated Diff Removal
  • Stale File Replacement
  • Skip CI Intermediate
  • CI Log Deduplication
  • Web Fetch Summarization
  • Context Forgetting
  • File Query Routing
  • On-Demand Diff

Resilience & Recovery

  • Model Fallback
  • Overload Retry
  • Forced Verification
  • Error Files Editable

Hallucination Prevention

  • Web Search
  • URL Fetching
  • Anti-Hallucination Prompts
  • GITAUTO.md Restrictions
  • Review Response Guardrails

Ready to improve your test coverage?

Go from 0% to 90% test coverage with GitAuto. Start for free, no credit card required.

Install FreeContact Sales

Product

  • Home
  • Why GitAuto
  • What GitAuto Does
  • How It Works
  • Use Cases
  • How to Get Started
  • Solution
  • Pricing
  • Pricing Details
  • ROI Calculator
  • ROI Methodology
  • FAQ
  • Blog
  • Contact

Dashboard

  • Dashboard
  • Coverage Trends
  • File Coverage
  • Credits
  • Open PRs
  • Usage
  • Triggers
  • Actions
  • References
  • Rules
  • CircleCI Integration
  • npm Integration

Documentation

  • Docs
  • Getting Started
  • Setup
  • Triggers
  • Coverage Setup
  • Customization
  • How It Works
  • Auto Merge
  • CircleCI
  • npm

Legal

  • Privacy Policy
  • Terms of Service

Connect

  • GitHub
  • LinkedIn
  • Twitter
  • YouTube
GitAuto Logo© 2026 GitAuto, Inc. All Rights Reserved