Update Bitbucket cloud UpdatePullRequest to properly able to close PR - #203
Conversation
…in order to resolve issue in PR closing
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthrough
ChangesBitbucket Cloud pull request updates
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to Closed Bitbucket Cloud pull requests now apply metadata changes before being declined, so changes such as title updates are retained when closing. No actionable current-head risk remains. Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
…ges (like title) before closing the PR

BB cloud UpdatePullRequest api works a bit different and needs a dedicated api in order to close PRs.
This is required for BB cloud integration tests coverage jfrog/frogbot#1421
go fmt ./...for formatting the code before submitting the pull request.Summary by CodeRabbit
Bug Fixes
Tests