Last updated: June 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.
This feature is only available on Pro subscription tiers or higher. See pricing options.
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.
Note: Automations currently supports cloud integrations. Self-hosted support will be added in a future update.
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 .
- Name your automation.
- Choose GitHub or GitLab from the Provider dropdown.
- Pick the target repository.
- (Optional) Enable for draft pull requests by checking the box.
Note: Creating an automation sets up a webhook on the repository. You’ll need the appropriate permissions.
Set Conditions
Conditions define when an action is triggered. GitKraken currently supports:
- File location
- File contents
- Pull request
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.
Note: A file path includes folders, e.g. src/app/index.ts, while a file name is just index.ts.
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:
- Add comment: Posts a comment on the PR.
- Add to checklist: Adds checklist items to the PR description.
- Add assignee: Assigns the PR to selected users and can include a message.
- Add label: Applies a GitHub label to the PR.
- Add reviewer: Assigns a reviewer or team, with an optional message.
Note: Authors can’t review their own PRs. If selected, GitKraken will skip that step and apply all others.
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 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:
