Get a weekly pull request summary in Linear
Staying on top of pull requests requires routine checking of GitHub. Instead, Notis automatically generates a weekly summary in Linear every Monday morning so your code review queue is visible when you plan your week.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List Linear issues
Lists non-archived linear issues; if project id is not specified, issues from all accessible projects are returned. can also filter by assignee id to get issues assigned to a specific user.
Why this helps
Neurodivergent founders often need structured routines to stay on top of work. Without a weekly PR review summary appearing automatically in Linear, code review work gets deprioritized and PRs age without being addressed.
- See all open PRs in Linear every week
- No need to manually check GitHub for review work
- Stay proactive about code review queue
- Built-in routine for code review planning
Setup
Build it in a few focused steps.
- 1Connect GitHub and Linear to Notis.
- 2Create the automation: 'Every Monday morning at 9am, fetch all open pull requests and add a summary to a Linear issue with links to each PR.'
- 3Select your notification channel.
- 4Choose the trigger: Notis Cron (weekly).
- 5Wait for the first Monday to see the summary appear in Linear.
Questions about this workflow
Can I change the day and time for the digest?
Yes. Your prompt can specify any day and time that works for your team's schedule, e.g., 'every Friday at 4pm.'
Should I include closed PRs or just open ones?
By default, this tracks open PRs. You can customize your prompt to also include recently closed ones if you prefer.
Can I filter by branch or author?
Yes. Your prompt can narrow the digest to specific branches, authors, or labels.
Should I include review status or just list PRs?
Notis can include review status, so you see which PRs are approved, pending, or need work.
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 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.