From 2a0617cd7903e169b6931cdd04990b151fc2ab4a Mon Sep 17 00:00:00 2001 From: Siddhant Medar Date: Tue, 14 Apr 2026 16:43:59 -0500 Subject: [PATCH] fix: escape colon in WARNING message to prevent YAML mapping parse The unquoted ': ' (colon + space) in 'WARNING: AI review step failed' was being interpreted as a YAML mapping key-value separator, causing the entire script item to be parsed as a dict instead of a command string. Bitbucket then rejected it with 'Missing or empty command string' error at pull-requests > feature/* > 2 > step > script > 9. Replaced the colon with a hyphen. Validated with yaml.safe_load that all 10 script items in the ai-code-review step now parse as strings. --- bitbucket-pipelines.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bitbucket-pipelines.yml b/bitbucket-pipelines.yml index fb95627..b8ac02d 100644 --- a/bitbucket-pipelines.yml +++ b/bitbucket-pipelines.yml @@ -139,7 +139,7 @@ definitions: # apt-get above is still a hard failure (rare in practice). # AI review is advisory, not a gate. - export PR_URL="https://bitbucket.org/${BITBUCKET_WORKSPACE}/${BITBUCKET_REPO_SLUG}/pull-requests/${BITBUCKET_PR_ID}" - - cd code-review-agent && python main.py "$PR_URL" || echo "WARNING: AI review step failed (non-blocking)" + - cd code-review-agent && python main.py "$PR_URL" || echo "WARNING - AI review step failed (non-blocking)" # =============================================================================