Spot benchmark trends and mark the GitHub issue
Have Notis check Bench history on a schedule and keep the related issue marked when performance drifts.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
A gradual performance decline can be easy to miss when benchmark history lives apart from the issue that needs attention.
- Review historical benchmark results on a recurring schedule.
- Apply a visible label when a trend meets your criteria.
- Keep the follow-up tied to a GitHub issue you identify.
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 named Bench benchmark history and add a specified label to the GitHub issue if your stated trend threshold is met.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real benchmark history and issue.
Questions about this workflow
Does Bench provide the threshold for a regression?
You need to state the threshold or decision rule in your instruction. Notis can review the history Bench provides against that rule.
Can it label an issue without an issue reference?
Provide the repository and issue to update in your instruction or automation context.
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.