Keep release access aligned with current priorities
Your repository permissions should follow the work your team is actually doing.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Add team access restrictions
Overwrites the list of teams (and their child teams) granted push access to a protected branch; the list of team slugs must be provided in the http post request body.
Why this helps
Team access rules become stale as competitive priorities shift, creating unnecessary permission requests and confusion.
- Keeps protected branch access aligned with active ownership
- Reduces permission-request interruptions
- Makes release responsibility easier to understand
Setup
Build it in a few focused steps.
- 1Connect Similarweb digitalrank api and GitHub to Notis once through the portal.
- 2Create an automation or ask Notis to update protected-branch team access according to the current Similarweb competitive release roadmap.
- 3Choose a monthly or weekly Notis cron trigger.
- 4Select a reporting channel and test it with one protected branch.
Questions about this workflow
Will this change repository permissions broadly?
No. Scope the instruction to the named protected branch and approved team list.
Can the roadmap be reviewed before changes happen?
Ask Notis to report proposed differences first if your process needs a review step.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Similarweb digitalrank api to GitHub. A trigger fires from one place; an action lands in another.
Similarweb digitalrank api 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.
Similarweb digitalrank api 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.