Workflow origin for the Azure DevOps pull request comment closure loop. It reads one Azure DevOps repository, pull request, and current thread comments for context, creates exactly one owner-provided top-level thread comment through recued-core.azure-devops.pull_request.thread.create, and when the thread succeeds it seeds durable data.shared closure state for azure-devops-pull-request-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not complete, abandon, approve, vote on, edit, retarget, assign reviewers to, delete, or otherwise mutate Azure DevOps pull requests.
Comment on Azure DevOps pull request with closure watch
Workflow origin for the Azure DevOps pull request comment closure loop. It reads one Azure DevOps repository, pull request, and current thread comments for context, creates exactly one owner-provided top-level thread comment through recued-core.azure-devops.pull_request.thread.create, and when the thread succeeds it seeds durable data.shared closure state for azure-devops-pull-request-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not complete, abandon, approve, vote on, edit, retarget, assign reviewers to, delete, or otherwise mutate Azure DevOps pull requests.
Complete workflow
Azure DevOps Pull Request Comment Closure Loop
4 pinned recipes
Workflow pack for Recued-created Azure DevOps pull request comments. It composes the Azure DevOps capability pack with a closure ledger: add one owner-approved top-level thread comment to an existing Azure DevOps pull request, persist only the connection/organization/project/repository/pull-request/thread linkage in data.shared, and let a scheduled watcher re-read that exact pull request until Azure DevOps reports it completed or abandoned. This pack does not replace Azure DevOps pull request comments, native notifications, review approvals, completion or abandon controls, branch policies, builds, service hooks, or general code review reporting; it adds Recued-visible closure state for pull request comments 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.
Scheduled adopter for Azure DevOps pull request comment closure rows seeded by comment-azure-devops-pull-request-with-closure. It lists only Recued-originated pull-request-comment watches, re-reads a bounded batch of Azure DevOps pull request, and closes the shared row when Azure DevOps reports that pull request completed or abandoned. It can notify the owner on terminal pull request state, but it never creates, updates, approves, votes on, completes, abandons, deletes, resolves, comments on, edits branches for, changes reviewers on, or otherwise mutates Azure DevOps pull requests.
Low-frequency timeout role for recued-core/azure-devops-pull-request-comment-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.
Owner-visible list/close role for recued-core/azure-devops-pull-request-comment-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.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (43 steps)
organization_value
trim
Trim whitespace from setting organization
project_value
trim
Trim whitespace from setting project
repository_id_value
trim
Trim whitespace from setting repository id
comment_text_value
trim
Trim whitespace from setting comment text
has_connection
compare
Check if setting azure devops has data
has_organization
compare
Check if organization value has data
has_project
compare
Check if project value has data
has_repository_id
compare
Check if repository id value has data
has_pull_request_id
compare
Check if setting pull request id does not equal 0
has_comment_text
compare
Check if comment text value has data
skip_pull_request_read
any
Check if any of the conditions are true
repository
?
skip: step.skip_pull_request_read equal true
pull_request
?
skip: step.skip_pull_request_read equal true
pull_request_status
default
Apply default
has_pull_request_status
compare
Check if pull request status has data
pull_request_status_norm
lowercase
Convert pull request status to lowercase
pull_request_completed
compare
Check if pull request status norm equals completed
pull_request_abandoned
compare
Check if pull request status norm equals abandoned
pull_request_terminal_before_comment
any
Check if any of the conditions are true
skip_thread_context
any
Check if any of the conditions are true
threads_raw
?
skip: step.skip_thread_context equal true
existing_threads
default
Apply default
thread_count_before_create
count
Count items in existing threads
skip_thread_create
any
Check if any of the conditions are true
created_thread
?
skip: step.skip_thread_create equal true
created_thread_id
default
Apply default
has_created_thread
compare
Check if created thread id has data
created_at
date_add
Add 0 days to
raw_pull_request_key
join
Join items with ":"
pull_request_key_colon
replace
Replace text in raw pull request key
pull_request_key_slash
replace
Replace text in pull request key colon
pull_request_key_dot
replace
Replace text in pull request key slash
pull_request_key_at
replace
Replace text in pull request key dot
pull_request_key_space
replace
Replace text in pull request key at
pull_request_key_left_angle
replace
Replace text in pull request key space
pull_request_key_right_angle
replace
Replace text in pull request key left angle
pull_request_key_plus
replace
Replace text in pull request key right angle
pull_request_key_equals
replace
Replace text in pull request key plus
pull_request_key_question
replace
Replace text in pull request 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_azure_devops_pull_request_comment_closure_watch
?
skip: step.skip_closure_seed equal true
summary
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
project
setting
=
azure devops
setting
=
comment text
setting
=
organization
setting
=
repository id
setting
=
pull request id
setting
=
0
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.