Keep Dependabot Secret Access Up to Date
Use a scheduled review to process repository access recorded for Dependabot secrets in AnyDB.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Add selected repo to org secret
Grants an existing repository access to an existing organization-level dependabot secret; the repository must belong to the organization, and the call succeeds without change if access already exists.
Why this helps
A recorded approval can remain disconnected from the secret access needed by a repository.
- Process outstanding access records in batches
- Keep repository access requests from being forgotten
- Avoid separate manual checks for already granted access
Setup
Build it in a few focused steps.
- 1Connect AnyDB and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to review approved AnyDB records and grant each specified repository access to the existing organization Dependabot secret.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real approved record.
Questions about this workflow
Can the repository be outside the organization?
No. The repository must belong to the organization that owns the Dependabot secret.
What if access was granted already?
The GitHub operation succeeds without change when access already exists.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link AnyDB to GitHub. A trigger fires from one place; an action lands in another.
AnyDB 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.
AnyDB 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.