Use “Comment on GitHub issue with closure watch” in Recued. It carries out the named workflow using the connections and settings you choose.
Comment on GitHub issue with closure watch
Use “Comment on GitHub issue with closure watch” in Recued. It carries out the named workflow using the connections and settings you choose.
Complete workflow
GitHub Issue Comment Closure Loop
4 pinned recipes
Use GitHub Issue Comment Closure Loop in Recued for issues, comments, developer workflow, and closed loop. It includes 2 ready-to-run workflows and 1 related pack in one install.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Use “GitHub issue comment closure watcher” in Recued. It checks saved items on a schedule and updates them when the connected service reports a final status.
Use “GitHub issue comment closure watcher timeout” in Recued. Low-frequency timeout role for the connected service. It moves a limited batch of expired rows from active to timedout, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.
Use “GitHub issue comment closure watcher lifecycle review” in Recued. It carries out the named workflow using the connections and settings you choose.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (39 steps)
repo_value
trim
Trim whitespace from setting repo
github_repo_parts
split
Split repo value into parts
issue_number_value
trim
Trim whitespace from setting issue number
comment_body_value
trim
Trim whitespace from setting comment body
has_connection
compare
Check if setting github has data
has_repo
compare
Check if repo value has data
has_issue_number
compare
Check if issue number value has data
has_comment_body
compare
Check if comment body value has data
skip_issue_read
any
Check if any of the conditions are true
issue
?
skip: step.skip_issue_read equal true
state
default
Apply default
has_issue_state
compare
Check if state has data
pull_request_url
default
Apply default
issue_is_pull_request
compare
Check if pull request url has data
issue_already_closed
compare
Check if state equals closed
skip_comment_context
any
Check if any of the conditions are true
comments_raw
?
skip: step.skip_comment_context equal true
comments
default
Apply default
comment_count_before_create
count
Count items in comments
skip_comment_create
any
Check if any of the conditions are true
created_comment
?
skip: step.skip_comment_create equal true
created_comment_id
default
Apply default
has_created_comment
compare
Check if created comment id has data
created_at
date_add
Add 0 days to
raw_issue_key
join
Join items with ":"
issue_key_colon
replace
Replace text in raw issue key
issue_key_slash
replace
Replace text in issue key colon
issue_key_dot
replace
Replace text in issue key slash
issue_key_at
replace
Replace text in issue key dot
issue_key_space
replace
Replace text in issue key at
issue_key_left_angle
replace
Replace text in issue key space
issue_key_right_angle
replace
Replace text in issue key left angle
issue_key_plus
replace
Replace text in issue key right angle
issue_key_equals
replace
Replace text in issue key plus
issue_key_question
replace
Replace text in issue 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_comment_closure_watch
?
skip: step.skip_closure_seed equal true
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
repo
setting
=
github
setting
=
comment body
setting
=
issue number
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.