Smart Label Sync: From Linear Comments to GitHub
Conversations in Linear often highlight what an issue really needs (urgent, blocked, review-needed). Notis watches those comments and auto-labels the GitHub issue so the right people see it.
Trigger
Comment Received Trigger
Triggered when a comment is received.
Action
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
Important context lives in Linear comments, but GitHub issue labels stay stale. Team members hunting through GitHub can't see that something is blocked or needs immediate review because the labels were never updated.
- Reduce manual label updates by letting comments drive labels automatically
- Keep GitHub issue visibility aligned with actual Linear discussion
- Help team members quickly spot blocked or priority work without opening Linear
- Reduce missed updates that happen when someone discusses priorities verbally but forgets to update both tools
Setup
Build it in a few focused steps.
- 1Connect Linear and GitHub to Notis
- 2Create an automation with: 'When someone comments on a Linear issue mentioning "blocked" or "urgent", add the corresponding label to GitHub'
- 3Set trigger to 'Linear comment received'
- 4Notis will learn common keywords from your team's language (e.g., 'needs review', 'hotfix', 'blocked')
- 5Test by commenting on a Linear issue and watching GitHub labels update
Questions about this workflow
Can I use my team's custom label names?
Yes. Just mention them in your automation prompt: 'add GitHub labels like frontend-critical or backend-blocker based on the discussion'.
What if a comment mentions multiple priorities?
Notis can handle it. You can set it to add multiple labels: 'if the comment mentions urgent or critical, add the urgent label; if it says blocked, add blocked'.
Does this replace label automation rules in GitHub?
It complements them. Use this for dynamics that emerge in conversation, and use GitHub branch protection rules for code review requirements.
Will old comments trigger labels retroactively?
No, automations only act on new events going forward. This keeps you focused on current work.
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.