Handle Codespaces access without another checklist
Small developer-environment requests are easy to postpone. Make the approved request the source of truth and let Notis carry it through.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add a selected repository to a user secret
Grants a specified repository access to an authenticated user's existing codespaces secret, enabling codespaces created for that repository to use the secret.
Why this helps
Codespaces setup stalls when secret access depends on a founder remembering a one-off repository change.
- Reduces setup delays
- Keeps access requests tied to written approval
- Removes another small task from the mental queue
Setup
Build it in a few focused steps.
- 1Connect Rosette text analytics and GitHub to Notis once through the portal.
- 2Create a portal automation or ask Notis to process approved Codespaces secret requests.
- 3Use this instruction: Extract the repository and secret request from the incoming text and grant access only when the request explicitly names an existing authenticated-user Codespaces secret and approval.
- 4Select an incoming webhook trigger, choose the run-report channel, and test with a low-risk repository.
Questions about this workflow
Does it create a new secret?
No. The GitHub action grants a repository access to an existing Codespaces secret.
What if approval is missing?
Notis can report the request as incomplete instead of changing access.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Rosette text analytics to GitHub. A trigger fires from one place; an action lands in another.
Rosette text analytics 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.
Rosette text analytics 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.