Automations

Last updated: December 2025

Use GitKraken.dev Automations to create rule-based workflows that trigger actions when pull requests and issues match specific conditions. Automations help you streamline collaboration and enforce consistency across teams.

Automation examples

Here are a few ways teams are using Automations to reduce manual effort and create scalable workflows:

• Safe deployments: Add a checklist for database migrations.
• Critical code reviews: Assign reviewers to high-impact areas like payments.
• Security checks: Flag sensitive changes (e.g., auth) for review.
• Refactoring guardrails: Prevent conflicts and schedule follow-ups.
• SOC 2 compliance: Automate tasks for encryption and security checks.
• DevOps enhancements: Enforce quality checks and automate infrastructure changes.

Get started with automations

Log in at gitkraken.dev and select Automations in the left menu. If it’s your first time, you’ll see the get started page with the option to create a new automation or use a suggested template.

Create an automation

Click + Create Automation.

1. Name your automation.
2. Choose from the Provider dropdown.
3. Pick the target repository.
4. (Optional) Enable for draft pull requests by checking the box.

Set Conditions

Conditions define when an automation is triggered. GitKraken currently supports the following condition types:

• Pull request content
  Trigger on PR metadata, activity, or discussion.

• Review: Status
  Watch for approvals, missing reviews, or stale feedback.

• Branch and origin
  Trigger based on the source or target branch, or the repository.

• CI/CD checks
  React to build, test, and deployment outcomes.

• File condition
  Match file paths, folders, or specific code snippets.

• GitKraken AI
  Analyze pull request diffs and metadata to detect conditions you care about.

Boolean logic

You can choose whether all or any of the conditions must be true.

File location conditions

• File name: Matches file names.
• File path: Matches full file paths.
• File added in folder: Triggers when a new file is added to a specified folder in a PR.

File contents conditions

• Old code: Matches the red (left side) of a split diff.
• New code: Matches the green (right side) of a split diff.
• New and old code: Matches both sides.

Pull request conditions

• Number of changed files
• PR author
• PR labels

Actions

GitKraken supports these automation actions:

AI

• GitKraken AI
  Post a comment with a summary generated from an AI prompt.

People

• Notify user
  Send a custom notification to selected users.

• Add reviewer
  Assign a reviewer or team, with an optional message.

• Add assignee
  Assign the PR to selected users, optionally including a message.

• Remove reviewer
  Unassign a reviewer or team from the PR.

• Remove assignee
  Unassign a user from the PR.

Pull Request

• Add comment
  Post a comment on the PR.

• Add label
  Apply a GitHub label to the PR.

• Close PR
  Automatically close the pull request.

• Add to checklist
  Add checklist items to the PR description.

Manage saved automations

Once you’ve created automations, manage them at GitKraken.dev.

You can:

• Enable/disable
• Edit
• Delete
• Duplicate
• Sort by status or action

Edit, delete, or duplicate

Use the icon next to an automation name.

Sort automations

Sort by Status (enabled/disabled) or Action (type of triggered automation).

Add another automation

Click + Create Automation again from the list view.

Repository management

The Repository Management screen shows which repos have active automations, who created them, the provider, and automation counts.

Admins can also add/remove repos or perform bulk actions.

Next Steps

Explore more ways to automate and streamline Git workflows:

• Connect an Integration
• Use Launchpad to manage PRs and issues
• Visualize metrics with GitKraken Insights
• Return to GitKraken.dev Support Home