Keep issue comment discussions up to date

Comments get edited and reactions get added in GitHub but those updates don't flow to Linear, leading to stale conversations. Notis automatically syncs comment updates so your Linear issues reflect the full current state of discussions.

Trigger

GitHub Issue Comment Changed

Triggers when a specific GitHub issue comment changes. Monitors the following fields for changes: - ``body`` -- the text content of the comment (detects edits) - ``updated_at`` -- the last-updated timestamp - ``reactions_*`` -- all individual reaction counts (thumbs up/down, laugh, confused, heart, hooray, eyes, rocket) and the total count When a change is detected, the payload includes the full current comment data plus a ``changed_fields`` list indicating exactly which fields were modified.

Linear logo

Action

Create a comment

Creates a new comment on a specified linear issue.

Why this helps

When comment edits and reactions don't sync between GitHub and Linear, team members reading from Linear miss important clarifications or changes to context that happened in GitHub.

  • Issue discussions stay current in Linear
  • Comment edits and reactions automatically sync
  • Team always sees the latest discussion context
  • No stale conversations in Linear

Setup

Build it in a few focused steps.

  • 1Connect GitHub and Linear to Notis.
  • 2Create the automation: 'When a GitHub issue comment is edited or gets reactions, update the corresponding Linear comment with the latest content and reaction counts.'
  • 3Select your notification channel.
  • 4Choose the trigger: GitHub Issue Comment Changed.
  • 5Test by editing a GitHub issue comment and verify it updates in Linear.

Questions about this workflow

Should I track all reactions or just important ones?

You can include all reactions or filter to specific types like emoji reactions that add context.

What if the Linear comment has local edits?

Notis can append updates as new comments rather than overwriting, preserving any local Linear edits.

Can I include edit history?

Yes. Notis can note that a comment was edited and include the update timestamp.

Should I delete Linear comments if they're deleted on GitHub?

You can configure this based on your preference. Default behavior is to archive them rather than delete.

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 logo

GitHub triggers

Linear logo

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.

TriggerPolling

Create linear attachment

Creates a new attachment and associates it with a specific, existing linear issue.

ActionInstant

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.

TriggerPolling

Create a comment

Creates a new comment on a specified linear issue.

ActionInstant

New Branch Created

Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.

TriggerPolling

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.

ActionInstant

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.

TriggerPolling

Get create issue default params

Fetches a linear team's default issue estimate and state, useful for pre-filling new issue forms.

ActionInstant

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.

TriggerPolling

Create a label

Creates a new label in linear for a specified team, used to categorize and organize issues.

ActionInstant

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.

TriggerPolling

Delete issue

Archives an existing linear issue by its id, which is linear's standard way of deleting issues; the operation is idempotent.

ActionInstant

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.

TriggerPolling

Get all teams

Retrieves all teams from the linear workspace without requiring any parameters.

ActionInstant

Commit Event

Triggered when a new commit is pushed to a repository.

TriggerInstant

Download issue attachments

Downloads a specific attachment from a linear issue; the `file name` must include the correct file extension.

ActionInstant

Connect any two apps with Notis in the middle.

Not just GitHub and Linear. 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 Linear.