Turn Bench regression reports into GitHub issue labels
Send a benchmark report to Notis and keep the matching GitHub issue clearly marked for follow-up.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
Benchmark regressions can get buried when their status is not reflected on the GitHub issue tracking them.
- Make regressions easier to spot in an issue list.
- Use Bench results to decide whether an issue needs a regression label.
- Avoid manually updating issue labels after reviewing a benchmark report.
Setup
Build it in a few focused steps.
- 1Connect Bench and GitHub once in the Notis portal.
- 2Create an automation in Automations, then New Automation.
- 3Tell Notis to review the Bench benchmark report and add a regression label to the GitHub issue you name only if the report shows a regression.
- 4Pick a webhook trigger and choose where run reports should go.
- 5Test with one real report and issue.
Questions about this workflow
Does Bench start this automation directly?
Bench has no listed trigger events. A Notis webhook starts the automation, and Notis can then review Bench results.
Which GitHub issue will be labeled?
Name the repository and issue in your instruction or webhook request so Notis can target the intended issue.
Can this create a label that does not exist?
The GitHub action can add labels and creates labels that do not already exist.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bench to GitHub. A trigger fires from one place; an action lands in another.
Bench triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Bench and GitHub, 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 GitHub.