Gitar automation: From suggested fixes to auto-merge

Overview

This course walks you through the progressive path to automation in Gitar, and the guardrails that keep Gitar's agentic automation and approval within your control. You'll learn to set approval criteria, tie those criteria to merge-blocking thresholds, and decide exactly where to draw the line before Gitar can approve, commit, or merge a request without a manual review.

Learning objectives

After completing this course, you'll be able to:

• Describe the progressive automation path in Gitar.
• Enable auto-apply for suggested fixes.
• Configure block merges based on a severity threshold.
• Configure auto-approve using natural-language criteria.
• Set up auto-merge against your blocking thresholds.

Key topics

• Automating code reviews
• Automating pull/merge requests

Target audience

• Administrators
• Analysts
• Developers
• DevOps engineers
• Engineering leaders
• Stakeholders

Prerequisites

• Active Gitar account connected to your supported DevOps platform, such as GitHub, GitLab, Azure DevOps, or Bitbucket.
• Administrative permissions in Gitar to enable merge blocking and other features (to set automation at the organization or repo level, the relevant permissions are needed at that respective level).
• For GitHub users: auto-merge allowed in your GitHub organization settings.