Process approved Borneo requests for GitHub secret access
When a Borneo request identifies an organization, secret, and repository, update that secret's selected repository access list.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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 valid access request can linger while someone manually finds the organization secret and updates its repository list.
- Reduce repetitive updates to selected repository access lists.
- Tie an access change to a supplied Borneo request.
- Avoid repeated work when repository access is already granted.
Setup
Build it in a few focused steps.
- 1Connect Borneo and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Tell Notis to apply only approved requests, using the supplied organization, secret name, and repository to grant selected repository access.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one approved request for an existing organization secret configured for selected repositories.
Questions about this workflow
Does this create a secret?
No. The selected GitHub action adds a repository to an existing organization secret whose visibility is set to selected.
What does the Borneo request need to identify?
It should supply the organization, the existing secret name, the repository, and an approval signal or policy that your instruction can use.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Borneo to GitHub. A trigger fires from one place; an action lands in another.
Borneo 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.
Borneo 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.