Keep repository access aligned with role changes
When responsibilities shift, turn the access needed for the new role into a clear GitHub update.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
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.
Why this helps
A role change can leave someone waiting for access to the repository tied to their new responsibilities.
- Connect role context to a repository access update.
- Reduce delays when responsibilities change.
- Keep the person, repository, and permission explicit.
Setup
Build it in a few focused steps.
- 1Connect Breathe HR and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation.
- 3Tell Notis to review supplied role-change details and add the specified person as a collaborator on the named repository with the intended permission.
- 4Choose a recurring schedule as the trigger and select where run reports should go.
- 5Test with one real role change and verify the access update.
Questions about this workflow
Does it remove the person's previous repository permissions?
No. This action adds or updates access for the specified repository. It does not remove access elsewhere.
What should be supplied for a successful update?
Include the person's GitHub username, repository owner and name, and intended permission level where applicable.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Breathe HR to GitHub. A trigger fires from one place; an action lands in another.
Breathe HR 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.
Breathe HR 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.