Automatic Issue Assignment Sync: Linear to GitHub
The moment a Linear issue is assigned to you, the matching GitHub issue gets the same assignee. Your codebase always reflects who is responsible for each task.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
Add assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Why this helps
Issues get assigned in Linear but nobody notices they're also open in GitHub. Work gets orphaned on one platform while someone waits on the other.
- Eliminate duplicate assignment notifications across tools
- Prevent tasks from falling through the cracks between Linear and GitHub
- Keep ownership and accountability synchronized in real-time
- Reduce the back-and-forth of 'did you see this assigned?'
Setup
Build it in a few focused steps.
- 1Ensure both Linear and GitHub are connected to Notis
- 2Create a new automation with the prompt: 'When an issue is assigned in Linear, add that person as an assignee in the corresponding GitHub issue'
- 3Set the trigger to 'Linear issue properties updated' (captures assignment changes)
- 4Choose your notification channel (Slack works well for quick confirmations)
- 5Test by assigning yourself a task in Linear and checking that GitHub reflects the change within moments
Questions about this workflow
What if the person assigned in Linear isn't a GitHub collaborator?
Notis will alert you via your notification channel that the sync couldn't complete because that user isn't in GitHub yet. It's a good reminder to onboard them or adjust the assignment.
Does this work if the GitHub issue doesn't exist yet?
Best practice: first ensure your Linear-to-GitHub issue sync is running (so issues exist in both places), then add this assignment sync as a second automation. Together they keep everything in sync.
Can I unassign someone and have it sync to GitHub too?
Yes. Your automation prompt can say 'sync assignments and unassignments' to keep both tools aligned.
Does this sync reassignments, or only the first assignment?
Every change syncs. If an issue moves from Alice to Bob in Linear, GitHub gets updated to show Bob within seconds.
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.