Pull Request and Issue Workflow Automation

Save time   Reduce mistakes   Enforce policies


How It Works



1. Create Rules
  • Assign myself to urgent issues
    Trigger
    Issue

    Labeled


    Conditions
    Labels
    Include Any Of:

    urgent


    Actions
    Add Assignees

    stevertigo

    [Empty]

2. Automate Workflow

Recipes

Git Butler has a flexible rule editor that allows you to define rules on issues and pull requests.

Here are a few uses cases of what it can be used for and how to set up the rules.

Smart pull request classification

Pull requests can be labeled based on their title, body, contents of the files they change, etc.


WHEN:

A new pull request is opened that touches files in the client/

DO:

Add label "frontend" to the pull request

What it looks like in Git Butler:

  • Tag frontend code with label
    Trigger
    Pull Request

    Opened


    Conditions
    Affected Files
    Some Match

    /.*/client/.*/


    Actions
    Add Labels

    frontend

    [Empty]

Pricing

Git Butler is always free for open source projects.
Private repositories are charged per runs, where a run is a successful execution of a rule.


Free

$0


Runs

100 per month

Support

Community

Rules

Unlimited

Repositories

Unlimited

Collaborators

Unlimited

Starter

$20

Per mo / Billed Annually

Runs

1000 per month

Support

Email

Rules

Unlimited

Repositories

Unlimited

Collaborators

Unlimited

Pro

$100

Per mo / Billed Annually

Runs

10000 per month

Support

Phone & Email

Rules

Unlimited

Repositories

Unlimited

Collaborators

Unlimited

FAQ


What triggers, conditions, and actions does Git Butler currently support?

Git Butler supports all Issue- and Pull Request-related triggers (Opened, Closed, Reopened, Assigned, Labeled, etc.), conditions (State, Body, Title, Author, Assignees, Labels, Milestone, etc.), and actions (Add Assignees, Add Labels, Set Milestone, Add Comment, Close, etc.)


When are you going to add support for X?

We are constantly working on expanding the set of triggers, conditions and actions we support, as well as adding integrations with 3rd party services. If you want to see something in Git Butler, please drop us a line at hi@gitbutler.com and we'll do our best to prioritize it.


How does Git Butler compare to GitHub Actions?

GitHub Actions is a very powerful platform that allows deep automation of your git workflow from idea to production. However, it requires that you code everything you need. By contrast, Git Butler allows you to automate your git workflow by creating powerful rules using a simple visual editor.


Why does Git Butler’s GitHub app require access to my code?

Git Butler needs access to your pull requests’ diff contents, so it can run rules on them. Git Butler does not and will never store your code or read any of it for any purpose other than to evaluate and run your rules.
Write access is only needed to facilitate the merge action for pull requests.


Automate your workflow now!