Apply branch check decisions without losing them between tools
Record the repository, branch, and approved check contexts in Todoist. Notis updates the protected branch in GitHub.
Trigger
New Task Created
Trigger when a new task is added to Todoist.
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
A new CI check may be agreed upon but never added to branch protection after the planning conversation ends.
- Turn governance decisions into action
- Keep branch requirements current
- Avoid manual settings navigation
Setup
Build it in a few focused steps.
- 1Connect Todoist and GitHub to Notis once.
- 2Ask Notis to add the status check contexts listed in a new approved Todoist task to the named protected branch.
- 3Choose New Task Created and a channel for run feedback.
- 4Test with a check context that has already reported on a non-critical protected branch.
Questions about this workflow
Can I add a check that has never run?
No. GitHub requires the status check context to have been reported previously before it can be added.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Todoist to GitHub. A trigger fires from one place; an action lands in another.
Todoist triggers
GitHub actions
New Task Created
Trigger when a new task is added to Todoist.
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 Todoist and GitHub. Any combination from 1,000+ 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.