Cooper&Wright vs Sentry's Seer
Seer finds the root cause of a Sentry issue and opens a fix PR for it, inside Sentry, one issue at a time, and it is good at it. Cooper&Wright starts where that ends. Its unit of work is the pull request, and it covers the pull requests Seer never sees: the ones people open, and Dependabot's.
- Unit of work
- A Sentry issue.
- A pull request that lands.
- Where it runs
- Inside Sentry.
- On GitHub, as an App, on the PR and its checks.
- Ends at
- A fix PR.
- A green PR you merge, or a bounded hand-off with the reason.
- Pull requests it sees
- The ones it opens.
- Those, the ones people open, and Dependabot's.
- When you overrule it
- The issue is closed.
- It reads your fix against its own and keeps the rule.
It stays on the pull request
Opening the fix is the first step, not the last. Cooper&Wright watches the pull request's checks, reads the failing job's log, and pushes a fix for what failed, round by round. Rounds are bounded at three: if the checks are still red after that, it stops and writes the reason on the row, and nothing is pushed again until you press Retry.
It watches the pull requests it did not open
PR failure monitoring fixes the failing checks on the pull requests your team opens, on their own branch. Dependabot auto-merge fixes Dependabot's pull requests and merges them once every check is green, behind the merge gate you choose. Neither needs a Sentry project.
It learns when you overrule it
When you close its fix or push your own over it, Cooper&Wright reads your fix against its own and keeps the rule. The rule goes into its next fixes for that repository, and climbs to all your repositories on the same stack when another of them teaches it too. How lessons work.
Common questions
What does Cooper&Wright do that Seer does not?
It stays on the pull request after it opens it: it watches the checks, fixes what fails for up to three rounds, and hands off with the reason if they are still red. It also watches the pull requests people open and Dependabot's, and when you overrule a fix it reads yours against its own and keeps the rule.
Does it need Sentry?
The Sentry fixes do. PR failure monitoring and Dependabot auto-merge work on any GitHub repository you connect, with or without a Sentry project.
What does it cost?
Nothing while it is in beta, and no card. The planned Pro tier is $49 a month for three repositories.