Discussion-Driven Workflow: Linear Comments to GitHub Issues
A critical comment about a missing feature or blocker is posted in a Linear issue thread. Notis watches for keywords like 'need to', 'blocker', or 'urgent', and creates a new GitHub issue to track it.
Trigger
Comment Received Trigger
Triggered when a comment is received.
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
Important work gets discussed in Linear comments but never formally tracked as its own issue. It lives only in the conversation, easily missed or forgotten when the original issue is closed.
- Capture work that emerges from discussion before it's forgotten
- Ensure all real work gets its own issue for visibility and tracking
- Prevent important context from being lost when parent issues close
- Enable asynchronous work capture—teams can mention work in comments and Notis ensures it's tracked
Setup
Build it in a few focused steps.
- 1Connect Linear and GitHub to Notis
- 2Create an automation: 'When a comment on a Linear issue mentions a blocker, missing feature, or critical task, create a new GitHub issue for it'
- 3Configure keywords: 'if comment says need to, blocker, critical, urgent, or must-fix, create an issue'
- 4Set trigger to 'Linear comment received'
- 5Customize the new GitHub issue: 'add a link back to the original Linear comment and prefix title with the keyword that triggered creation'
- 6Test by posting comments with trigger words and verifying GitHub issues are created
Questions about this workflow
How do I prevent accidental issue creation from casual mentions?
Use specific keywords: 'only create issues if the comment says "need to fix" or contains the label-tag #create-issue'.
Can I review the issue before it's created?
Notis creates it automatically, but you can always delete it in GitHub if it was a false trigger. Alternatively, set up a Slack notification first to review before creation.
Should the new issue link back to the original Linear issue?
Yes, your automation can include: 'add a comment in the GitHub issue linking back to the Linear issue and the specific comment that triggered creation'.
Can this work across multiple Linear teams?
Yes, one automation handles all teams. Or create team-specific automations if you want different rules per team.
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.