Complete secret access rollout tasks without GitHub settings detours
Name the organization, repository, and existing secret in Todoist. Notis grants selected repository access and reports completion.
Trigger
New Task Created
Trigger when a new task is added to Todoist.
Action
Add selected repository to an organization secret
Adds a repository to an organization secret's access list when the secret's visibility is 'selected'; this operation is idempotent.
Why this helps
A newly onboarded repository can fail its first deployment because shared secret access was one unchecked rollout detail.
- Prevent missed rollout dependencies
- Make access requests explicit
- Use an idempotent GitHub operation
Setup
Build it in a few focused steps.
- 1Connect Todoist and GitHub in Notis.
- 2Create an automation prompt that grants a repository access to the existing organization Actions secret named in a new Todoist rollout task.
- 3Pick Todoist New Task Created and a reporting channel.
- 4Test using a selected-access secret and a repository you administer.
Questions about this workflow
What must already be configured?
The organization secret must exist and its visibility must be set to selected repositories.
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.