Refresh hardware assumptions after every PR update
New commits can change the performance story. Get refreshed hardware context before the next review pass.
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
Get Hardware Data
Retrieve mining hardware data from minerstat including hashrates, power consumption, and specifications. Use this tool to get benchmark data for GPUs and ASIC miners to compare mining performance across different hardware. Filter by type (gpu/asic) or brand to narrow results. Combine both filters together to avoid mixed variants with differing hashrate and power draw values.
Why this helps
Reviewers may rely on stale hardware assumptions after a pull request changes.
- Refresh benchmark context after meaningful code changes.
- Reduce stale performance assumptions.
- Make resumed reviews faster.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Minerstat once through the Notis portal.
- 2Create the automation in the portal, or ask Notis to create it in plain language.
- 3Tell Notis to retrieve Minerstat hardware data for the models referenced by the pull request whenever a new commit is added, then summarize changed performance assumptions.
- 4Select the new commit on pull request trigger, choose a reporting channel, and test with one new PR commit.
Questions about this workflow
What hardware can it cover?
Minerstat provides benchmark data for GPUs and ASIC miners, with type and brand filters.
Why run after each commit?
It refreshes context at the point when review assumptions may have changed.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Minerstat. A trigger fires from one place; an action lands in another.
GitHub triggers
Minerstat actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Coins Data
Retrieves mining coin data from minerstat API including hashrates, difficulty, rewards, and prices. Use this tool to get current mining statistics for cryptocurrencies. You can filter results by specific coin tickers (e.g., 'BTC,ETH') or by mining algorithms (e.g., 'SHA-256,Ethash'). Returns data such as network hashrate, difficulty, estimated mining rewards, current price, and trading volume for each coin. Note: `difficulty` and network hashrate fields may be null for some coins; validate their presence before using in calculations.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Hardware Data
Retrieve mining hardware data from minerstat including hashrates, power consumption, and specifications. Use this tool to get benchmark data for GPUs and ASIC miners to compare mining performance across different hardware. Filter by type (gpu/asic) or brand to narrow results. Combine both filters together to avoid mixed variants with differing hashrate and power draw values.
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 Pools Data
Retrieve mining pool data from minerstat. Requires an authenticated minerstat connection. Returns a list of mining pools with their supported coins, fees, payout thresholds, and other details. Use to discover pools for a specific coin or explore all available mining pools.
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.
Get Worker Activity
Retrieve activity logs for a specific worker for the last 3 days. Returns online/offline events, errors, and other activity for troubleshooting worker uptime issues or auditing worker behavior. The API key is automatically extracted from the Authorization header.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get Worker Data
Retrieve detailed real-time data for a specific mining worker. This tool fetches comprehensive information about a worker including: - Current status (online/offline/idle) - Hardware info (GPUs/ASICs with temperatures, fans, power) - Mining info (coin, pool, client software) - Hashrate data (current hashrates for main/dual/CPU mining) - Share statistics (accepted, rejected, stale) - Revenue estimates Use this when you need detailed metrics for a specific worker. The worker name must exactly match a worker configured in the minerstat dashboard. Returns found=False if the worker doesn't exist.
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 Minerstat, 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 Minerstat.