Code Review Access Automation: Linear Requests to GitHub
Comment in Linear 'need code review from @jane' and Notis adds Jane as a GitHub collaborator instantly. She can review immediately without access delays.
Trigger
Comment Received Trigger
Triggered when a comment is received.
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
Someone asks for code review in a Linear discussion but the reviewer isn't a GitHub collaborator. They can't review because they lack repo access, and waiting for manual permission wastes the reviewing momentum.
- Remove access delays from the code review process
- Enable external reviewers or temporary team members to contribute immediately
- Maintain focus on the review rather than permission management
- Reduce friction for asynchronous code review workflows
Setup
Build it in a few focused steps.
- 1Connect Linear and GitHub to Notis
- 2Create an automation: 'When someone comments in a Linear issue mentioning @username for code review, add them as a GitHub collaborator with read or write access'
- 3Customize permission level: 'grant collaborators write access so they can push suggestions'
- 4Set trigger to 'Linear comment received'
- 5Test by commenting on a Linear issue with @reviewer_name and verifying GitHub access is granted
- 6Your reviewer can now immediately jump into the GitHub PR without waiting
Questions about this workflow
Should reviewers get write or read access?
Depends on your process. Write access lets them push fixes directly; read-only if you want them to suggest through comments. Specify in your automation: 'grant read-only access' or 'grant write access'.
What if I don't want to grant access just from a mention?
Adjust the automation to be more specific: 'only add them if the Linear issue is tagged with needs-review' or 'only if they're mentioned with @review-needed'.
Can I remove access after the review is complete?
Yes. Create a follow-up automation: 'When a Linear issue is marked Done, remove temporary collaborators and keep only permanent team members'.
Does this work for external contractors?
Absolutely. That's a key use case—invite external reviewers immediately without waiting for manual permission.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to GitHub. A trigger fires from one place; an action lands in another.
Linear triggers
GitHub actions
Comment Received Trigger
Triggered when a comment is received.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Issue Created Trigger
Triggered when a new issue is created.
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.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
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.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
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.
Project Created
Fires when a new Linear project is created. Covers projects in both public and private teams — polls with the connected user's token, so visibility matches what the connected user can see in Linear.
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.
Project Properties Updated
Fires when properties on a Linear project change (status, lead, target date, priority, etc.). Covers projects in both public and private teams — polls with the connected user's token.
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.
Not just Linear and GitHub. Any combination from 985+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business GitHub.