Keep launch branch checks current
A protected branch is only helpful when it protects the right things. Let scheduled maintenance keep launch checks aligned.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Required checks drift as campaign workflows change, creating surprises at the point of release.
- Reduces branch protection drift
- Makes release expectations clearer
- Avoids manual settings audits
Setup
Build it in a few focused steps.
- 1Connect BulkPublish and GitHub to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it conversationally.
- 3In one instruction, tell Notis to add the required status check contexts to protected branches for repositories supporting active BulkPublish campaigns.
- 4Pick a recurring trigger and a channel for run reports.
- 5Test on one protected branch.
Questions about this workflow
Does this remove existing checks?
No. The GitHub action adds the requested contexts.
What should the instruction include?
Name the repositories, branches, and exact check contexts that matter for your campaign workflow.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link BulkPublish to GitHub. A trigger fires from one place; an action lands in another.
BulkPublish 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.
BulkPublish 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.