Owner-visible list/close role for recued-core/gitlab-issue-note-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.
GitLab issue note closure watcher lifecycle review
Owner-visible list/close role for recued-core/gitlab-issue-note-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.
Complete workflow
GitLab Issue Note Closure Loop
4 pinned recipes
Workflow pack for Recued-created GitLab issue notes. It composes the GitLab capability pack with a closure ledger: add one owner-approved public note to an existing GitLab issue, persist only the connection/project/issue/note linkage in data.shared, and let a scheduled watcher re-read that exact issue until GitLab reports it closed. This pack does not replace GitLab issue comments, native notifications, issue state controls, boards, milestones, webhooks, or general issue reporting; it adds Recued-visible closure state for issue notes 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 GitLab issue note closure loop. It reads one GitLab issue and current comment notes for context, creates exactly one owner-provided public note through recued-core.gitlab.issue.note.create, and when the note succeeds it seeds durable data.shared closure state for gitlab-issue-note-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create, update, close, reopen, delete, move, label, assign, or otherwise mutate GitLab issues.
Scheduled adopter for GitLab issue note closure rows seeded by comment-gitlab-issue-with-closure. It lists only Recued-originated issue-note watches, re-reads a bounded batch of GitLab issue, and closes the shared row when GitLab reports that issue closed. It can notify the owner on closure, but it never creates, updates, closes, reopens, deletes, moves, labels, assigns, comments on, or otherwise mutates GitLab issues.
Low-frequency timeout role for recued-core/gitlab-issue-note-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.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Data fetch
active_rows
?
timed_out_rows
?
closed_rows
?
▼
Process (10 steps)
close_key
trim
Trim whitespace from setting close key
close_is_timed_out
starts_with
Check if close key starts with data.shared.recipe.recued-core_gitlab-issue-note-closure.timed_out.
close_is_closed
starts_with
Check if close key starts with data.shared.recipe.recued-core_gitlab-issue-note-closure.closed.
close_allowed
any
Check if any of the conditions are true
close_terminal_row
?
skip: step.close_allowed not_equal true
lifecycle_rows
flatten
Flatten nested lists in
shown_rows
slice
Take a subset of
row_count
count
Count items in lifecycle rows
table
to_table
Format results as a data table
summary
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
close key
setting
=
row limit
setting
=
50
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.