Skip to content
Notis

Research new commits added to pull requests

Stay oriented when a PR changes after you have started reviewing it.

Trigger

New Commit Added to Pull Request

Triggers when a new commit is pushed to a specific pull request. Monitors all commits on the specified pull request and emits an event for each newly added commit. This covers force-pushes and additional commits pushed to the PR's head branch.

Action

/api/x402/research

AI-powered Token Deep Research API

Why this helps

Additional commits can invalidate an earlier review plan and make it unclear what deserves attention now.

  • Focus on what changed since the prior review point.
  • Reduce repeated reading of unchanged code.
  • Keep review follow-up aligned with the latest commit.

Setup

Build it in a few focused steps.

  • 1Connect GitHub and www.capminal.ai to Notis once through the portal.
  • 2Create the automation in Automations or ask Notis to create it conversationally.
  • 3Use this instruction: Research each new commit added to a GitHub pull request and explain the likely purpose of the change, what review attention it may need, and how it relates to the existing PR.
  • 4Select the new commit added to pull request trigger and choose a reporting channel.
  • 5Test with one follow-up commit.

Questions about this workflow

Does it run for every added commit?

Yes. The GitHub trigger emits an event for each newly added commit on the monitored pull request.

Can it focus on a specific pull request?

Yes. Configure the trigger for the pull request you want to monitor.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link GitHub to www.capminal.ai. A trigger fires from one place; an action lands in another.

GitHub triggers

www.capminal.ai actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

/api/x402/research

AI-powered Token Deep Research API

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

TriggerPolling

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.

TriggerPolling

New Branch Created

Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.

TriggerPolling

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.

TriggerPolling

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.

TriggerPolling

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.

TriggerPolling

Connect any two apps with Notis in the middle.

GitHub and www.capminal.ai, 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 www.capminal.ai.