Review private vulnerability reporting on a schedule
Make repository security settings easier to remember with a recurring status check and run report.
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
Security settings can go unchecked when they depend on someone remembering to revisit repository configuration.
- Create a recurring reminder with a current status result.
- Keep repository security review visible in run reports.
- Reduce reliance on memory for a periodic check.
Setup
Build it in a few focused steps.
- 1Connect GitHub once in the Notis portal; connect Ably too if you want it available for related agent context.
- 2Create an automation in the portal or tell Notis to create one from any channel.
- 3In one instruction, ask Notis to check private vulnerability reporting for the repository you name and summarize the returned status.
- 4Choose a recurring schedule and where run reports should go.
- 5Test with one real repository.
Questions about this workflow
Does the check change repository settings?
No. This action checks the status; it does not enable or disable the setting.
Can the schedule check every repository automatically?
Name the repository or repositories in your instruction. This action checks a specified repository, and the workflow should not assume a repository inventory that has not been provided.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Ably to GitHub. A trigger fires from one place; an action lands in another.
Ably 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.
Ably 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.