Compare the options behind every new pull request
Make review decisions with evidence, not just the loudest comment.
Trigger
New Pull Request Created
Triggers when a new pull request is created in GitHub, matching the optional configured filters. Emits an event for each newly created pull request. Supports filtering by repository, owner/organisation, author, assignee, label, state, base branch, head branch, and draft status.
Action
Compare options
Weigh several products, vendors, or approaches.
Why this helps
Founders often review unfamiliar technical choices while juggling product, sales, and operations.
- Surface viable alternatives before approving a direction.
- Reduce lengthy back-and-forth during review.
- Make technical tradeoffs easier to explain to collaborators.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Deep research to Notis once through the portal.
- 2Create the automation in the portal or tell Notis the desired outcome conversationally.
- 3Write one instruction asking Deep research to compare the PR approach with alternatives, including tradeoffs, risks, cost, and maintenance.
- 4Pick the new pull request trigger, select a channel for reports, and test with one open PR.
Questions about this workflow
Does this replace code review?
No. It adds research around the decision so human review can focus on the code and context.
What options can it compare?
It can compare libraries, architectures, vendors, implementation patterns, or other approaches described in the PR.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Deep research. A trigger fires from one place; an action lands in another.
GitHub triggers
Deep research actions
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Research a company
Get a sourced brief before a call.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
Compare options
Weigh several products, vendors, or approaches.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Deliver it later
The report arrives as a follow-up message when it is ready.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Commit Event
Triggered when a new commit is pushed to a repository.
Connect any two apps with Notis in the middle.
Not just GitHub and Deep research. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Deep research.