Weekly Backlog Sync: Linear to GitHub on Schedule
Every Monday morning, Notis syncs your complete Linear backlog to GitHub. Backlog issues become GitHub issues, blocked items get labeled, and priorities are reflected. Your team starts the week with both tools in perfect sync.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
By mid-week, Linear and GitHub have drifted. New issues exist in Linear but not GitHub. Some tasks are marked done in one tool but still open in the other. Coordinating across both requires manual spot-checking.
- Batch sync once a week rather than managing constant manual updates
- Start each week with a clean, synchronized view of all work
- Reduce drift and confusion from working with stale data
- Give neurodivergent team members a structured weekly reset point
Setup
Build it in a few focused steps.
- 1Connect Linear and GitHub to Notis
- 2Create an automation: 'Every Monday at 8 AM, sync all unresolved Linear issues to GitHub'
- 3Customize the sync scope: 'sync only issues in specific projects or with certain labels'
- 4Set notification to alert your #engineering channel when the weekly sync completes
- 5On the first run, Notis reports how many issues were synced and surfaces any conflicts
- 6Team verifies the sync looks correct and adjusts the automation prompt if needed
Questions about this workflow
What time should we run the weekly sync?
Pick a time when your team typically starts work. Monday at 8 AM works for most teams, but you can say 'Tuesday at 9 AM' or 'Friday at 4 PM' instead.
Does this delete GitHub issues that were resolved in Linear?
No, it marks them as completed or closed. Your prompt can specify: 'close GitHub issues that are marked Done in Linear'.
What if someone makes local changes to a GitHub issue between syncs?
The sync will respect existing GitHub data and merge carefully. Your prompt can say 'don't overwrite GitHub descriptions if they've been manually edited'.
Can I run the sync more often than weekly?
Yes, change the cron to daily or every 12 hours, but weekly is typical for most teams to avoid notification fatigue.
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.