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.
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
Copy
Ask AI
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)
Copy
Ask AI
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
Copy
Ask AI
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
Copy
Ask AI
Whenever a PR is opened, add @username1 as a reviewer.
5. Add a reviewer to a PR (complex)
Copy
Ask AI
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
Copy
Ask AI
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
Copy
Ask AI
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
Copy
Ask AI
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.