Keep CI requirements in sync with engineering decisions
The right checks should become part of the path, not a reminder in a document.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add status check contexts
Adds status check contexts (provided in the request body, e.g., `{"contexts": ["new-context"]}`) to a protected branch, requiring these contexts to have been previously reported.
Why this helps
Teams agree that a check is required, but branch protection is never updated.
- Reduces accidental policy gaps
- Makes CI expectations enforceable
- Removes repetitive settings work
Setup
Build it in a few focused steps.
- 1Connect Manus and GitHub to Notis once through the portal.
- 2Create the automation or ask Notis to create it in plain language.
- 3Instruct Notis: When Manus approves a new CI requirement, add the specified previously reported status check contexts to the matching protected GitHub branch.
- 4Pick an incoming webhook trigger, choose the report channel, and test with one existing status context.
Questions about this workflow
Must the status check already exist?
Yes. GitHub requires the context to have been previously reported.
Can multiple checks be added?
Yes. The Manus request can name several contexts in one approved change.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Manus to GitHub. A trigger fires from one place; an action lands in another.
Manus 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.
Manus 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.