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

Dashboard Trigger

Trigger GitAuto from the coverage dashboard by selecting specific files. This method provides a visual interface for targeted test generation with coverage data insights.

Why use the dashboard trigger?

Visual File Selection: Browse your repository files with coverage percentages displayed, making it easy to identify which files need tests.

Bulk Operations: Select multiple files at once and create PRs for all of them simultaneously, saving time on large repositories.

Perfect for: Teams managing large codebases and QA managers tracking coverage metrics systematically.

How to use the dashboard trigger

1

Sign in to the GitAuto dashboard

Click the "Sign in" button in the top right corner and authenticate with your GitHub account.

Screenshot of the GitAuto dashboard sign in page with the sign in button
2

Select your repository

Select your GitHub organization and repository from the dropdown menus. Only repositories where GitAuto is installed will be displayed.

Screenshot showing the repository selection interface with organization and repository dropdowns
3

Browse repository files

The dashboard displays a list of files in your repository. If you've integrated coverage reports, you'll see coverage percentages for each file.

Screenshot showing the file list view with coverage percentages and selection checkboxes
4

Select files and generate tests

Check the boxes next to the files you want to generate tests for, then click the "Actions" button and select "Create PRs" to trigger GitAuto.

Screenshot showing file selection with checkboxes and the Actions button

Usage Cost

1 Pull Request - Each trigger creates one pull request with generated tests.

Ready to explore your codebase? Visit the coverage dashboard and start selecting files for targeted test generation. Or learn more about the coverage dashboard to see how to use the coverage dashboard. Once you start improving your coverage, track your progress with the Coverage Charts

Dashboard Looking Empty?

Empty coverage in your dashboard usually means your coverage reports aren't making it through the pipeline. It's like having a beautiful sports car with no gas. Let's get your data flowing!

Contact us and fill up that dashboard!

Review Comment TriggerCoverage Dashboard

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