Give New Pull Request Reviewers the Context They Need
When the reviewer list changes, DeepSeek creates a concise handoff tailored to the new review moment, including unresolved questions and likely focus areas.
Trigger
GitHub Pull Request Reviewers Changed
Triggers when the list of requested reviewers (users or teams) for a pull request changes — for example when a reviewer is added, removed, or re-requested. The payload includes the full current reviewer list (users and teams with details), which reviewers were added, which were removed, and the previous reviewer list for reference.
Action
Create Chat Completion
Tool to create a chat completion using DeepSeek models (deepseek-chat or deepseek-reasoner). Use when you need to generate AI responses to chat conversations. Supports streaming, tool/function calling, and various parameters to control generation behavior (temperature, max_tokens, etc.).
Why this helps
Adding or re-requesting a reviewer rarely includes enough context, forcing them to reconstruct the reason they were pulled in.
- Reduce reviewer ramp-up time
- Explain why review is being requested now
- Keep unresolved decisions visible across handoffs
Setup
Build it in a few focused steps.
- 1Connect GitHub and DeepSeek in Notis.
- 2Ask Notis to prepare a handoff note whenever requested reviewers change on a pull request.
- 3Use one prompt requesting added and removed reviewer context, unresolved decisions, risk areas, and a short review request, then select GitHub Pull Request Reviewers Changed.
- 4Tell Notis where to post the handoff note, then add or re-request a reviewer on a test pull request.
Questions about this workflow
Does it cover team reviewers?
Yes. The trigger includes reviewer users and teams, along with additions, removals, and the previous list.
Can it tailor context to a specialist reviewer?
Yes. Tell Notis to emphasize the area implied by the reviewer or team when that context is available.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to DeepSeek. A trigger fires from one place; an action lands in another.
GitHub triggers
DeepSeek actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Anthropic Message
Tool to create a model response using DeepSeek's Anthropic-compatible API format with support for system prompts, tool calling, streaming, and thinking mode. Use when you need to generate chat completions using the Anthropic Messages API format. Requires base_url='https://api.deepseek.com/anthropic' or metadata base_url ending with '/anthropic'. Supports extended thinking, function calling with tools, and streaming responses. Note: Images and documents are not supported in content blocks.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Chat Completion
Tool to create a chat completion using DeepSeek models (deepseek-chat or deepseek-reasoner). Use when you need to generate AI responses to chat conversations. Supports streaming, tool/function calling, and various parameters to control generation behavior (temperature, max_tokens, etc.).
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.
Get User Balance
Tool to get user's current account balance including granted and topped-up balances with detailed breakdown by currency (CNY or USD). Use when you need to check if the user has sufficient balance for API calls or to view detailed balance information.
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.
List Models
Tool to list currently available DeepSeek models and provides basic information about each one such as the owner and availability. Use when you need to discover which models are available for API calls.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
Connect any two apps with Notis in the middle.
GitHub and DeepSeek, or any other 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 DeepSeek.