Keep protected branch access aligned with delivery teams
The right team should be able to move quickly without widening access by accident.
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
Branch access becomes confusing when customer projects shift between internal teams and partners.
- Keeps team-based access current
- Reduces manual branch-policy edits
- Makes delivery ownership clearer
Setup
Build it in a few focused steps.
- 1Connect Delighted and GitHub to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it conversationally.
- 3Use this instruction: For active approved Delighted projects, overwrite protected branch push access with the teams authorized for that project and report any access change.
- 4Choose a recurring schedule, select a channel for run reports, and test with one active project.
Questions about this workflow
Does this replace the existing team list?
Yes. The GitHub action overwrites the teams granted push access, so the instruction should define the complete approved list.
Can it report changes before applying them?
Ask Notis to include a review report or approval condition in the instruction if your process requires it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Delighted to GitHub. A trigger fires from one place; an action lands in another.
Delighted 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.
Delighted 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.