Recued
Menu
← Back to recipes

Comment on Bitbucket pull request with closure watch

by recued-core v2 9 views

Use “Comment on Bitbucket pull request with closure watch” in Recued. It carries out the named workflow using the connections and settings you choose.

Complete workflow

Use Bitbucket Pull Request Comment Closure Loop in Recued for pull requests, comments, code review, and developer workflow. 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 “Bitbucket pull request comment closure watcher” in Recued. It checks saved items on a schedule and updates them when the connected service reports a final status.

bitbucketpull-requestscommentscode-review
by recued-core pinned v1

Use “Bitbucket pull request 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.

bitbucketwatchertimeoutowner-review
by recued-core pinned v1
View pack details, dependencies, and permissions →
How it works 40 steps

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 6 configurable

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

bitbucket setting =
repo slug setting =
workspace setting =
comment text setting =
pull request id setting = [object Object]
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.

Permissions it requires

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

Data it touches

Warehousedata.shared

About

Tags

bitbucket bitbucketpull-requestscommentscode-reviewdeveloper-workflowapprovalclosed-loopstate:bitbucket-pull-request-comment-closure-watcherpack:bitbucket-pull-request-comment-closure

Details

40 steps 6 configurable settings recipe_id: comment-pull-request-with-closure-bitbucket