Approval-gated Bitbucket Cloud pull request comment workflow. It reads the target repository and pull request for context, then creates exactly one top-level pull request comment through recued-core.bitbucket when comment text is present. It does not approve, request changes, decline, merge, edit comments, delete comments, resolve threads, change pull request metadata, run pipelines, or call arbitrary Bitbucket APIs.

How it works 9 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (9 steps)

■ workspace trim

Trim whitespace from setting workspace

■ repo_slug trim

Trim whitespace from setting repo slug

■ comment trim

Trim whitespace from setting comment

■ has_comment compare

Check if comment has data

■ repository ?

■ pull_request ?

■ created_comment ?

skip: step.has_comment not_equal true

■ skipped compare

Check if has comment does not equal true

■ card to_summary

Format results as a summary card

Settings 5 configurable

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

comment setting =

bitbucket setting =

repo slug setting =

workspace setting =

pull request id setting = 0