Wendy G Atlassian Team

Discussions

    • January Update - What's new in Bitbucket Forge

      Hi all, Our team has been working on quite a few new features in the past few months. In this post, we want to share a summary of all of them: * Two new UI modules (repoPullRequestOverviewPanel and repoCodeOverviewPanel) have been introduced. You now have more options to display information from your app in the Bitbucket…

    • Merge properties now available in on-merge checks invocation payload

      Hi all, As requested on https://jira.atlassian.com/browse/BCLOUD-23049 we have added a mergeProperties field to the invocation payload of bitbucket:mergeCheck Forge function triggered by on-merge trigger, it contains merge commit message amongst other properties related to a pull request merge. For details see…

    • Changes to required scopes for mergeCheck module and new on-reviewer-status-changed trigger

      Hi all, We want to share a few important updates on Custom Checks: * We added a new on-reviewer-status-changed trigger. * The bitbucket:mergeCheck module now requires the read:pullrequest:bitbucket scope. See the changelog for more details. We understand that changes in scope can be disruptive and we will always do our…

    • Scope check for bitbucket:mergeCheck module now enforced at runtime

      As mentioned in the previous post here, we are now enforcing read:pullrequest:bitbucket scope for bitbucket:mergeCheck module at runtime. If you have not already done so, please update your app to include this scope. See the latest changelog for more details. Thanks Wendy

Avatar