Turn Bugbug failures into clearly labeled GitHub issues
Get failed tests into the right triage lane without switching tools or sorting through reports by hand.
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
A failed test can be easy to miss when its report and the related GitHub issue live in separate tools.
- Make test-related issues easier to spot and sort.
- Reduce manual triage after a failed run.
- Let Notis infer an appropriate label from the report and issue context.
Setup
Build it in a few focused steps.
- 1Connect Bugbug and GitHub once in Notis.
- 2Create an automation in a channel or in Automations, then name it and choose a report channel.
- 3In one instruction, ask Notis to match each Bugbug failure to a related GitHub issue and add a relevant label.
- 4Pick the webhook trigger and choose where run reports go.
- 5Test with one real Bugbug failure and review the issue update.
Questions about this workflow
Does this create a GitHub issue for every failed test?
No. The selected action adds labels to an issue. Ask Notis to act only when it can identify a related issue, and to report when it cannot.
Do I have to configure label mappings?
No. Tell Notis in plain language how to interpret the failure and issue context. GitHub can create a label if the requested label does not already exist.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bugbug to GitHub. A trigger fires from one place; an action lands in another.
Bugbug 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.
Bugbug 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.