Keep CommCare repositories ready for private reports
A recurring check helps you spot a security-process gap before someone needs to report a vulnerability.
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 are easy to forget while operational priorities keep changing.
- Makes a critical repository setting visible
- Creates a low-effort security habit
- Reduces last-minute access and process confusion
Setup
Build it in a few focused steps.
- 1Connect CommCare and GitHub to Notis once through the portal.
- 2Create the automation or ask Notis to create it conversationally.
- 3Tell Notis in plain language to check private vulnerability reporting for the CommCare repository and report gaps.
- 4Select a recurring schedule and a run-report channel.
- 5Test it with the repository you rely on most.
Questions about this workflow
Can this check run monthly?
Yes. Use a recurring Notis schedule suited to your security review cadence.
Will it change the setting?
No. This workflow checks and reports the current status.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link CommCare to GitHub. A trigger fires from one place; an action lands in another.
CommCare triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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.
Not just CommCare and GitHub. Any 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.