Protect the brand release branch
Keep final brand changes limited to the people responsible for release quality.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add user access restrictions
Sets/replaces list of users allowed to push to a protected branch; usernames (e.g., `["user1"]`) must be a json array in request body (not schema parameters), an empty array `[]` removes all restrictions.
Why this helps
Protected branches lose their purpose when release access is not updated after a team change.
- Reduce accidental release changes
- Keep protected branch access current
- Make release ownership explicit
Setup
Build it in a few focused steps.
- 1Connect Brandfetch and GitHub once in Notis.
- 2Create an automation for brand release branch protection.
- 3Tell Notis to replace the protected branch's allowed GitHub usernames with the list approved in the Brandfetch release request.
- 4Choose a webhook trigger and report channel.
- 5Test with one protected branch and approved user list.
Questions about this workflow
Can the list be cleared?
Yes. An empty list removes all user restrictions for that protected branch.
What must the request identify?
Include the repository, protected branch, and approved usernames in the release request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Brandfetch to GitHub. A trigger fires from one place; an action lands in another.
Brandfetch 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.
Brandfetch 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.