Keep important pull request feedback from getting lost after merge
Not every review note belongs in the current change, but it still deserves a home. Notis captures deferred or explicitly flagged feedback in Linear while leaving ordinary review conversation in GitHub.
Trigger
New Pull Request Review Comment
Triggers when a new inline review comment is added to a specific GitHub pull request. Monitors all review comments across all reviews on the specified pull request and emits an event for each newly created comment. Edits to existing comments do not fire new events.
Action
Create linear issue
Creates a new issue in a specified linear project and team, requiring a title and description, and allowing for optional properties like assignee, state, priority, cycle, and due date.
Why this helps
Useful review feedback is often acknowledged with 'follow up later' and then disappears when the pull request closes and attention moves to the next task.
- Preserves deferred technical work without cluttering Linear with every review comment.
- Includes a direct link and code location so the follow-up starts with context.
- Lets reviewers signal durable work in GitHub without opening another app.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Linear to Notis once.
- 2Describe the rule in one instruction, for example: 'If a new PR review comment starts with follow-up, create a Linear issue with the comment and code location.'
- 3Pick New Pull Request Review Comment as the trigger and choose your run-report channel.
- 4Post one marked review comment on a test pull request and inspect the created issue.
Questions about this workflow
Will every inline comment create a Linear issue?
It does not have to. Use a phrase, repository, or other condition in the instruction so only comments that represent durable follow-up become issues.
Can the issue link back to the exact comment?
Yes. The trigger includes a direct URL to the GitHub review comment, which Notis can place in the Linear issue description.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Linear. A trigger fires from one place; an action lands in another.
GitHub triggers
Linear actions
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Create linear attachment
Creates a new attachment and associates it with a specific, existing linear issue.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
Create a comment
Creates a new comment on a specified linear issue.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Create linear issue
Creates a new issue in a specified linear project and team, requiring a title and description, and allowing for optional properties like assignee, state, priority, cycle, and due date.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Get create issue default params
Fetches a linear team's default issue estimate and state, useful for pre-filling new issue forms.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
Create a label
Creates a new label in linear for a specified team, used to categorize and organize issues.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Delete issue
Archives an existing linear issue by its id, which is linear's standard way of deleting issues; the operation is idempotent.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Get all teams
Retrieves all teams from the linear workspace without requiring any parameters.
Commit Event
Triggered when a new commit is pushed to a repository.
Download issue attachments
Downloads a specific attachment from a linear issue; the `file name` must include the correct file extension.
Connect any two apps with Notis in the middle.
Not just GitHub and Linear. Any combination from 1,000+ 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 Linear.