Give Bugbug failures a GitHub issue owner
Turn a test failure into a clear next step by putting the related issue in the right person's queue.
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
Test failures can linger when everyone assumes someone else will investigate the matching issue.
- Make ownership visible on related issues.
- Cut down on manual handoffs after failures.
- Avoid guessing when the report does not identify a clear owner.
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 failures to GitHub issues and assign the person indicated by the report or issue context.
- 4Pick the webhook trigger and choose where run reports go.
- 5Test with one real failure and confirm the assignee is appropriate.
Questions about this workflow
Will Notis invent an assignee if it cannot find one?
No. Instruct Notis to assign only when the report or issue context supports a clear choice, and otherwise report that the issue needs an owner.
What happens if the account cannot assign that person?
GitHub may ignore assignment changes when the authenticated user lacks push access. Review the run report and check repository access.
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.