Skip to content
Recued
Menu
← Back to recipes

Create GitHub issue with closure watch

by recued-core v1

Workflow origin for the GitHub issue closure loop. It reads the target repository for context, creates exactly one owner-approved issue through recued-core.github-pack.issue.create, and when the issue succeeds it seeds durable data.shared closure state for github-issue-closure-watcher. It uses deterministic owner-provided fields rather than AI and does not update, close, reopen, delete, transfer, label, assign, lock, comment on, create pull requests for, or otherwise mutate GitHub issues beyond the approved issue create.

Complete workflow

GitHub Issue Closure Loop 4 pinned recipes

Workflow pack for Recued-created GitHub issues. It composes the GitHub capability pack with a closure ledger: create one owner-approved issue in one repository, persist only the connection/repository/issue linkage in data.shared, and let a scheduled watcher re-read that exact issue until GitHub reports it closed. This pack does not replace GitHub issue state controls, issue views, project boards, milestones, native notifications, webhooks, pull request review, or general issue reporting; it adds Recued-visible closure state for issues Recued created.

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

Workflow origin for the GitHub issue closure loop. It reads the target repository for context, creates exactly one owner-approved issue through recued-core.github-pack.issue.create, and when the issue succeeds it seeds durable data.shared closure state for github-issue-closure-watcher. It uses deterministic owner-provided fields rather than AI and does not update, close, reopen, delete, transfer, label, assign, lock, comment on, create pull requests for, or otherwise mutate GitHub issues beyond the approved issue create.

githubissuesdeveloper-workflowrepository
by recued-core pinned v1
GitHub issue closure watcher
Background automation

Scheduled adopter for GitHub issue closure rows seeded by create-github-issue-with-closure. It lists only Recued-originated issue watches, re-reads a bounded batch of GitHub issue, and closes the shared row when GitHub reports that issue closed. It can notify the owner on closure, but it never creates, updates, closes, reopens, deletes, transfers, labels, assigns, locks, comments on, creates pull requests for, or otherwise mutates GitHub issues.

githubissuesdeveloper-workflowclosure
by recued-core pinned v1
GitHub issue closure watcher timeout
Background automation

Low-frequency timeout role for recued-core/github-issue-closure. It moves a bounded batch of expired rows from active to timed_out, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

githubwatchertimeoutowner-review
by recued-core pinned v1

Owner-visible list/close role for recued-core/github-issue-closure. It lists bounded active, timed-out, and closed rows. Supplying a timed-out or closed key deletes only that exact terminal row; active watches cannot be deleted here.

githubwatcherreviewclose
by recued-core pinned v1
View pack details, dependencies, and permissions →
How it works 32 steps

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

Process (32 steps)
repo_value trim
Trim whitespace from setting repo
title_value trim
Trim whitespace from setting title
body_value trim
Trim whitespace from setting body
has_connection compare
Check if setting github has data
has_repo compare
Check if repo value has data
has_title compare
Check if title value has data
skip_repository_read any
Check if any of the conditions are true
repository ?
skip: step.skip_repository_read equal true
repo_full_name default
Apply default
has_live_repo compare
Check if repo full name has data
repository_archived default
Apply default
skip_issue_create any
Check if any of the conditions are true
created_issue ?
skip: step.skip_issue_create equal true
created_issue_number default
Apply default
created_issue_id default
Apply default
has_created_issue_number compare
Check if created issue number has data
created_at date_add
Add 0 days to
raw_watch_key join
Join items with ":"
watch_key_colon replace
Replace text in raw watch key
watch_key_slash replace
Replace text in watch key colon
watch_key_dot replace
Replace text in watch key slash
watch_key_at replace
Replace text in watch key dot
watch_key_space replace
Replace text in watch key at
watch_key_left_angle replace
Replace text in watch key space
watch_key_right_angle replace
Replace text in watch key left angle
watch_key_plus replace
Replace text in watch key right angle
watch_key_equals replace
Replace text in watch key plus
watch_key_question replace
Replace text in watch key equals
skip_closure_seed any
Check if any of the conditions are true
closure_timeout_at date_add
Add setting no response timeout days days to
seed_github_issue_closure_watch ?
skip: step.skip_closure_seed equal true
summary to_summary
Format results as a summary card
Settings 5 configurable

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

body setting =
repo setting =
title setting =
github setting =
no response timeout days setting = 30

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

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

Data it touches

Warehousedata.shared

About

Tags

github githubissuesdeveloper-workflowrepositoryapprovalclosed-loopstate:github-issue-closure-watcherpack:github-issue-closure

Details

32 steps 5 configurable settings recipe_id: create-github-issue-with-closure