Priority Sync: Linear Changes to GitHub Visibility
Promote an issue to Urgent in Linear and Notis immediately updates the GitHub label to urgent-high. Demote it and the label changes to urgent-low. Engineers always see the current priority.
Trigger
Public Team Issue Properties Updated
Fires when properties on a *public-team* Linear issue change (status, assignee, priority, labels, etc.). For private teams (lock icon in Linear's sidebar) use `LINEAR_PRIVATE_TEAM_ISSUE_PROPERTIES_UPDATED`.
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
Priorities change frequently as work evolves, but GitHub labels stay stale. Engineers check GitHub and misjudge urgency because the label is outdated, leading to wrong prioritization.
- Ensure GitHub reflects current priorities without manual updates
- Help engineers quickly see what matters right now
- Reduce priority debates by having a single, synchronized source
- Keep the backlog visible and actionable in GitHub
Setup
Build it in a few focused steps.
- 1Connect Linear and GitHub to Notis
- 2Create an automation: 'When a Linear issue priority changes, update the GitHub urgency label'
- 3Map Linear priorities to GitHub labels in your prompt: 'Urgent -> urgent-high, High -> high-priority, Normal -> normal, Low -> backlog'
- 4Set trigger to 'Linear public team issue properties updated'
- 5Test by changing a Linear issue's priority and verifying GitHub label updates
- 6Your team can filter GitHub by priority label to see the current backlog order
Questions about this workflow
Should I use multiple labels or one label with a value?
GitHub supports both. Your automation can use separate labels (urgent-high, high-priority) or one label per priority level. Pick what works for your team.
What if GitHub doesn't have the label yet?
Notis will create it on first use. You can also pre-create labels in GitHub so they appear in the UI suggestions for consistency.
Can I also change GitHub project board columns based on priority?
Yes, create a complementary automation: 'When priority changes to Urgent, move the issue to the Urgent column in the GitHub project'.
Does this work with custom Linear priorities?
Yes. Map any Linear priority level to any GitHub label in your automation prompt.
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.