Pair scheduled Bugbug reviews with GitHub security checks
Review test health and the private vulnerability reporting status of the repositories you care about in one scheduled pass.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Check private vulnerability reporting status
Checks if private vulnerability reporting is enabled for the specified repository.
Why this helps
A regular test review can leave repository security settings unchecked when they live in a different tool.
- Bring test results and repository reporting status into one review.
- Surface repositories whose private reporting status needs attention.
- Reduce context switching during routine maintenance.
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 review recent Bugbug results and check private vulnerability reporting status for the related repositories.
- 4Pick the recurring schedule trigger and choose where run reports go.
- 5Test with one real repository and review the reported status.
Questions about this workflow
Does this enable private vulnerability reporting when it is off?
No. The selected GitHub action checks its status; it does not change the repository setting.
What does the schedule review use as its scope?
Specify the repositories or recent Bugbug results to include in your instruction. Notis should report if it cannot identify the related repositories.
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.