Skip to content
Notis

Close the planning loop when a GitHub pull request merges

Merging the code can be the final action. Notis recognizes the Linear identifier associated with the pull request and updates the issue, removing a small administrative step that is repeatedly easy to miss.

Trigger

Pull Request Updated

Triggers when an existing pull request is updated in a GitHub repository. Updates include title edits, description changes, label changes, assignee changes, reviewer requests, draft status changes, base branch changes, being closed, merged, or reopened. Only pre-existing PRs that receive an update will fire the trigger; newly created PRs are excluded. Supports optional filters: state, base branch, head branch, author, label, and draft status.

Action

Update issue

Updates an existing linear issue using its `issue id`; requires at least one other attribute for modification, and all provided entity ids (for state, assignee, labels, etc.) must be valid.

Why this helps

Finished engineering work stays open in Linear because updating the tracker feels less urgent than moving to the next problem, making the board steadily less trustworthy.

  • Keeps the Linear board aligned with what has actually merged.
  • Removes a repetitive end-of-task update at the moment attention is shifting.
  • Preserves a link from the completed issue to the merged implementation.

Setup

Build it in a few focused steps.

  • 1Connect GitHub and Linear in the Notis portal.
  • 2Ask Notis to create this automation with the instruction: 'When an existing pull request is merged, update the Linear issue referenced in it to our completed state.'
  • 3Pick Pull Request Updated as the trigger and choose the channel for confirmation reports.
  • 4Merge a test pull request that references a Linear identifier and verify the issue update.

Questions about this workflow

Does closing an unmerged pull request complete the issue?

No, if your instruction specifically requires the merged state. A closed-but-unmerged pull request can be ignored.

Can this use our team's own completed state?

Yes. Name the desired outcome in the instruction and Notis will update the linked issue using the valid Linear state for that team.

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.

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 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.