Skip to content
Recued
Get started
Menu
Publish Sign in GitHub
← Back to recipes

Watch Linear resolution for GitHub Actions handoff

by recued-core v1

Scheduled feedback half of the GitHub Actions to Linear exception handoff loop. It reads Linear issues created by create-approved-linear-issue-from-github-run, reads the original GitHub workflow run for current context, closes the Recued data.shared handoff when the Linear issue reaches a terminal state, and optionally notifies the owner to verify the current CI state. It does not update GitHub, rerun workflows, comment on GitHub, update Linear issues, create comments, change branch protection, or call arbitrary APIs. Linear Reviews, GitHub Actions notifications, logs, reruns, branch protection, Linear's GitHub integration, and GitHub issue syncing own normal CI operations; this watcher only records Recued-visible exception closure.

Complete workflow

CI Failure Handoff Loop - GitHub + Linear 3 pinned recipes

Workflow pack that closes the loop between exception-scoped GitHub Actions failures and owner-approved Linear follow-up work. It depends on the GitHub and Linear capability packs, detects one recent unhandled failed workflow run at a time, writes a data.shared proposal, notifies the owner, provides a manual action recipe that either creates the Linear issue and links it back to the GitHub workflow run or dismisses the proposal, and watches created Linear issues until they reach a terminal state. It excludes pull-request-attached runs by default because Linear Reviews already surfaces PR checks and CI-failure notifications. It does not replace GitHub Actions notifications, GitHub workflow logs, rerun controls, branch protection, Linear's GitHub integration, Linear PR automation, or GitHub issue syncing; use it only when those normal paths are insufficient and Recued-visible cross-system closure state is needed.

You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.

Watch Linear resolution for GitHub Actions handoff
This recipe Background automation

Scheduled feedback half of the GitHub Actions to Linear exception handoff loop. It reads Linear issues created by create-approved-linear-issue-from-github-run, reads the original GitHub workflow run for current context, closes the Recued data.shared handoff when the Linear issue reaches a terminal state, and optionally notifies the owner to verify the current CI state. It does not update GitHub, rerun workflows, comment on GitHub, update Linear issues, create comments, change branch protection, or call arbitrary APIs. Linear Reviews, GitHub Actions notifications, logs, reruns, branch protection, Linear's GitHub integration, and GitHub issue syncing own normal CI operations; this watcher only records Recued-visible exception closure.

githublineargithub-actionsci
by recued-core pinned v1
Propose Linear work for GitHub Actions failure
Background automation

Scheduled detection half of the GitHub Actions to Linear exception handoff loop. It reads recent failed workflow runs for one configured repository, excludes pull-request-attached runs by default, fetches failed job names for the first unhandled non-PR run, writes one data.shared proposal, and notifies the owner to review whether the failed run should become Linear work. It never creates Linear issues, comments on GitHub, reruns workflows, updates GitHub issues or pull requests, changes branch protection, mutates Linear projects, or calls arbitrary APIs. GitHub Actions notifications, workflow logs, rerun controls, branch protection, Linear Reviews, Linear's GitHub integration, and GitHub issue syncing own their normal paths; this recipe only creates a Recued-visible exception proposal that an owner can approve or dismiss with create-approved-linear-issue-from-github-run.

githublineargithub-actionsci
by recued-core pinned v1
Create approved Linear issue from GitHub Actions run

Owner-invoked action half of the GitHub Actions to Linear exception handoff loop. It reads one awaiting_owner_approval proposal written by github-linear-ci-failure-proposal, then either creates exactly one Linear issue from deterministic GitHub context or dismisses the proposal as no Linear work needed. Running this recipe is the owner's approval or decline. It re-reads the GitHub workflow run before creating Linear work and takes no outward-facing action when there is no pending proposal, the live workflow run no longer has conclusion failure, or the required Linear destination is missing. Linear Reviews, GitHub Actions notifications, workflow logs, rerun controls, branch protection, Linear's GitHub integration, and GitHub issue syncing should own the normal path.

githublineargithub-actionsci
by recued-core pinned v1
View pack details, dependencies, and permissions →
How it works 40 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Data fetch
▼ handoffs ?
▼
Process (39 steps)
■ handoffs_family filter
Filter by condition
■ created_handoffs filter
Filter by condition
■ handoffs_with_linear_issue filter
Filter by condition
■ candidate_rows slice
Take a subset of
■ watch_count count
Count items in handoffs with linear issue
■ has_candidate compare
Check if candidate rows has data
■ proposal_key default
Apply default
■ github_repo default
Apply default
■ github_run_id default
Apply default
■ github_run_number default
Apply default
■ github_workflow_name default
Apply default
■ github_run_url default
Apply default
■ linear_issue_id default
Apply default
■ linear_identifier default
Apply default
■ has_linear_issue compare
Check if linear issue id has data
■ has_repo compare
Check if github repo has data
■ has_run_id compare
Check if github run id is greater than 0
■ has_linear_connection compare
Check if setting linear has data
■ has_github_connection compare
Check if setting github has data
■ ready_to_read_linear all
Check if all conditions are true
■ linear_issue ?
skip: step.ready_to_read_linear not_equal true
■ linear_state_type default
Apply default
■ linear_state_name default
Apply default
■ linear_issue_url default
Apply default
■ linear_completed compare
Check if linear state type equals completed
■ linear_canceled compare
Check if linear state type equals canceled
■ linear_terminal any
Check if any of the conditions are true
■ ready_to_read_github all
Check if all conditions are true
■ github_run ?
skip: step.ready_to_read_github not_equal true
■ github_run_conclusion default
Apply default
■ github_run_status default
Apply default
■ github_current_url default
Apply default
■ now date_add
Add 0 minutes to
■ ready_to_close all
Check if all conditions are true
■ close_handoff ?
skip: step.ready_to_close not_equal true
■ notify_enabled compare
Check if setting notify owner equals true
■ should_notify all
Check if all conditions are true
■ send_owner_notification ?
skip: step.should_notify not_equal true
■ summary to_summary
Format results as a summary card
Settings 4 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

github setting =
linear setting =
channels setting = in_app
notify owner setting = true

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

Send notificationsRead your Github connectionRead your Linear connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

Data it touches

Warehousedata.issuedata.shared

About

recued-core

Tags

githublinear githubgithub-actionslinearcifailureexceptionwatcherresolutiondeveloper-workflowwork-trackingclosed-looppack:github-linear-ci-failure-handoff

Details

40 steps 4 configurable settings recipe_id: github-linear-ci-failure-resolution-watcher