Workflow origin for the Bitbucket pull request comment closure loop. It reads one Bitbucket pull request and current comments for context, creates exactly one owner-provided top-level comment through recued-core.bitbucket.pull_request.comment.create, and when the comment succeeds it seeds durable data.shared closure state for bitbucket-pull-request-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not approve, request changes, merge, decline, edit, resolve, delete, update pull request metadata, run pipelines, or otherwise mutate Bitbucket pull requests.
Comment on Bitbucket pull request with closure watch
Workflow origin for the Bitbucket pull request comment closure loop. It reads one Bitbucket pull request and current comments for context, creates exactly one owner-provided top-level comment through recued-core.bitbucket.pull_request.comment.create, and when the comment succeeds it seeds durable data.shared closure state for bitbucket-pull-request-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not approve, request changes, merge, decline, edit, resolve, delete, update pull request metadata, run pipelines, or otherwise mutate Bitbucket pull requests.
Complete workflow
Bitbucket Pull Request Comment Closure Loop
4 pinned recipes
Workflow pack for Recued-created Bitbucket pull request comments. It composes the Bitbucket capability pack with a closure ledger: add one owner-approved top-level comment to an existing Bitbucket pull request, persist only the connection/workspace/repository/pull-request/comment linkage in data.shared, and let a scheduled watcher re-read that exact pull request until Bitbucket reports it merged, declined, or superseded. This pack does not replace Bitbucket pull request comments, native notifications, review approvals, merge or decline controls, branch policies, pipelines, webhooks, 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 Bitbucket pull request comment closure rows seeded by comment-bitbucket-pull-request-with-closure. It lists only Recued-originated pull-request-comment watches, re-reads a bounded batch of Bitbucket pull request, and closes the shared row when Bitbucket reports that pull request merged, declined, or superseded. It can notify the owner on terminal pull request state, but it never creates, updates, approves, requests changes, merges, declines, deletes, resolves, comments on, runs pipelines for, or otherwise mutates Bitbucket pull requests.
Low-frequency timeout role for recued-core/bitbucket-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/bitbucket-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 (40 steps)
workspace_value
trim
Trim whitespace from setting workspace
repo_slug_value
trim
Trim whitespace from setting repo slug
comment_text_value
trim
Trim whitespace from setting comment text
has_connection
compare
Check if setting bitbucket has data
has_workspace
compare
Check if workspace value has data
has_repo_slug
compare
Check if repo slug 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
pull_request
?
skip: step.skip_pull_request_read equal true
state
default
Apply default
has_pull_request_state
compare
Check if state has data
pull_request_merged
compare
Check if state equals MERGED
pull_request_declined
compare
Check if state equals DECLINED
pull_request_superseded
compare
Check if state equals SUPERSEDED
pull_request_terminal_before_comment
any
Check if any of the conditions are true
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_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_bitbucket_pull_request_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.
bitbucket
setting
=
repo slug
setting
=
workspace
setting
=
comment text
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.