GitVertex automations are workspace-level rules that run against the repositories you choose. You'll find them on the Automations page in your workspace.

Who can manage automations

• Owners and Admins can enable, disable, and edit automations.
• Members can see the current automation state, but cannot change it.

Available automations

Merge-ready ping

Queues a Slack notification when a PR or MR becomes ready to merge, unless auto-merge is already enabled.

Settings:

• Slack destination — controlled by your workspace's Merge ready Slack notification rules
• Repositories — choose which repositories the rule applies to

Delete branch after PR is closed

Removes branches after PRs are closed so repositories stay cleaner.

Settings:

• Cadence — Instant or Daily
• Scope — Only merged PRs or Any closed PR
• Repositories — choose which repositories the rule applies to

Stale review reminder

Posts a reminder comment when a requested review has been waiting too long.

Settings:

• Default wait time — choose the standard number of days to wait
• Reviewer overrides — set custom wait times for specific reviewers
• Repositories — choose which repositories the rule applies to

Repository scoping

Each automation is scoped to one or more repositories. If a repository is not selected, the automation does not run for it.

The page also lets you filter the visible automation list by repository so you can inspect only the rules that affect a given codebase.

What to expect

• Enabled automations appear in the Enabled section with a short summary of behavior and repositories.
• Disabled automations stay in Available until you turn them on.
• Changes are saved per workspace, not per user.

Related pages

• Console
• Workspaces