Give benchmark regressions a clear GitHub owner
When a benchmark regression needs follow-up, have Notis assign the issue to the person you name.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Why this helps
A regression can be acknowledged without anyone being clearly responsible for the next step.
- Give a qualifying regression a named issue owner.
- Reduce manual handoffs after reviewing benchmark results.
- Keep ownership attached to the GitHub issue.
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 report and assign the named GitHub issue to the specified user only when your regression criteria are met.
- 4Pick a webhook trigger and choose where run reports should go.
- 5Test with one real report and issue.
Questions about this workflow
Will GitHub always accept the assignee?
GitHub may ignore assignment changes if the authenticated user lacks push access. The specified user also needs to be assignable in that repository.
Does this workflow find the issue automatically?
Provide the repository and issue reference, or include them in the webhook request.
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.