Automate Status Check Addition to Protected Branches
Weekly, Notis adds fresh status checks to your main branch to ensure all CI contexts pass. Your deployment pipeline stays current without you thinking about it.
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
Keeping status checks up to date with new CI tools is easy to forget. Neurodivergent founders need automated governance to prevent accidentally skipping critical checks.
- Status checks stay current without manual updates
- CI/CD requirements are always enforced on protected branches
- Reduces the risk of shipping untested code
- Automated governance frees mental energy from tracking CI tools
Setup
Build it in a few focused steps.
- 1Connect GitHub to Notis.
- 2Create an automation with the prompt: 'Every week, add these required status checks to the main branch: linting, tests, and security-scan.'
- 3Select Notis Cron (Weekly) as the trigger.
- 4Verify that the status checks are now listed as required on your main branch protection settings.
Questions about this workflow
What if a status check doesn't exist yet?
Notis will skip it until you create it in your CI system, or let you know that it's missing.
Can I add different checks to different branches?
Yes—create separate automations for develop, staging, and main with their own status check requirements.
Do these checks override existing ones?
No—Notis adds to the existing list. Any checks already required stay required.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Telegram to GitHub. A trigger fires from one place; an action lands in another.
Telegram triggers
GitHub actions
New Message Received
Triggered when your bot receives a new message in a private chat, group, or supergroup. To receive every message in a group, Privacy Mode must be disabled for the bot in BotFather.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
New Channel Post
Triggered when a new post is published to a channel where your bot is an administrator.
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.
Callback Query Received
Triggered when a user taps an inline keyboard button attached to one of your bot's messages.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Message Edited
Triggered when a message in a chat your bot can see is edited by its sender.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
New Chat Member
Triggered when a new member joins a group or supergroup the bot belongs to, including when the bot itself is added.
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 Telegram and GitHub. Any combination from 985+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business GitHub.