We’re hiring! Join our team as a Founding AI Engineer 🚀

React Workflows are workflows that are triggered by events in your repository. They take the form of “If X happens, then Ellipsis should do Y”.

They take the form of “If X happens, then Ellipsis should do Y”.

You define react workflows in the web UI using natural language; there’s no workflow builder, you simply describe what actions you want Ellipsis to take.

View what Ellipsis thought and did in the web UI

When a react workflow is triggered, Ellipsis will take the actions you’ve configured it to take.

View what Ellipsis thought and did in the web UI

​
Examples

Here are examples of what you can build with react workflows. Copy/paste these examples to get started building your own workflows.

1. Post a message to Slack when a PR is merged

When a PR is merged, post a message to the #engineering channel. The message should include the PR title, link, and a bullet point summary of the most important changes in the pull request.

2. Post a message to Slack when a PR is merged (complex)

When a PR is merged, if it was merged by @username1, @username2, or @username3, post a message to the #engineering channel. The message should include the PR title, link, and a bullet point summary of the most important changes in the pull request. Your message should also include a link to any associated Github issues and the number of lines added/removed. If the PR adds any database migrations, add an alert emoji to the message and call this out.

3. Comment on a PR without an associated issue

If a new pull request is opened that doesn’t link to an associated issue, leave a comment on the PR asking the author to link to an issue.

4. Add a reviewer to a PR

Whenever a PR is opened, add @username1 as a reviewer.

5. Add a reviewer to a PR (complex)

Whenever a PR is opened, that modifies the billing/pricing page, add @username2 as a reviewer. Only do this if the target branch is main.

6. Add conventional commit format title to PR

Whenever a PR is opened with a title that doesn’t follow the conventional commit format, update the title to follow the conventional commit format.

7. Send a slack message when a bug report is filed

Watch for new issues that are created, if someone opens an issue that appears to be a bug report, send a message to the #engineering-bugs channel.

8. Post an implementation plan to an issue

Every time a new issue is opened, attempt to understand the scope and required changes. Then post a comment containing an implementation for how an engineer would go about implementing the requested change.

​
Triggers

  • When a PR is opened
  • When a PR is opened (as a draft)
  • When a PR is closed (and possibly merged)
  • When an issue is opened
  • When an issue is closed

Reach out to us if you need to trigger workflows on other events.

​
Actions

These are the actions that Ellipsis can take.

  • Make a code change
  • Search the codebase
  • Search historical pull requests, issues, and commits
  • Post a message to Slack
  • Post a comment on a pull request
  • Add a reviewer to a pull request
  • Hide old comments on a pull request
  • Update the title of a pull request
  • Add a summary to the pull request body
  • Add a label to a pull request
  • Post a comment on an issue
  • Create a GitHub/Linear issue
  • Add a label to an issue
  • View Github/Linear issues

​
Debugging

You can view the thoughts and actions that Ellipsis took for any workflow run. Use this to debug and iterate on your workflows.

Start a free trial

Click here to start a free 7 day trial of AI Code Reviews & Bug Fixes