Wendy G Atlassian Team

Hi Dani, The Forge function linked to your web trigger will have web trigger event as well as the invocation context as the input params. workspaceId is available in the invocation context. In terms of repos, it depends on your use case but you can either pass the repo in as a query parameter to your web trigger URL and…

@Nikolai Marov FYI merge commit message is now available in mergeProperties field of on-merge checks payload, see https://community.atlassian.com/t5/Forge-for-Bitbucket-Cloud/Merge-properties-now-available-in-on-merge-checks-invocation/ba-p/2788758 for details.

Note we have started rollout of recommended checks feature to some of the workspaces that have opted into custom checks EAP, and will progressively roll it out more broadly in the coming week. You can configure a recommended check by selecting "Recommended" option on repo settings -> custom merge checks page. Unlike…

@Aron Gombas _Midori_ are you able to elaborate on your use case for rerunning a successful check? It is not currently possible to rerun successful checks, but depending on the use cases, we might look into extending the ways a check can be re-triggered in future, so it would help if you could tell us some more details on…

Required read:pullrequest:bitbucket scope on bitbucket:mergeCheck module is now enforced at runtime. See the latest changelog for more details.

@Aron Gombas _Midori_ I've raised https://jira.atlassian.com/browse/BCLOUD-23168 for you.

@Aron Gombas _Midori_ thanks for the feedback. Does this only happen when you approve/unapprove in quick succession? Or it just happens randomly? We are in the middle of making a bunch of UI changes including the card on PR page that shows the list of checks, I've raised a ticket on our backlog to investigate further to…

Hi @István Nagy @Fabian Siegel, Just to let you know that we've recently added workspaceId field in the context for custom UI/UI Kit 2, so you can access it in resolver context now. See https://developer.atlassian.com/cloud/bitbucket/changelog/#CHANGE-1296 for more details. Thanks Wendy

Hi Yuri, Yes this behaviour is as expected if you have not yet shared your app in developer console distribution page. To share the app: * Using the Forge CLI, deploy your app to the production environment. * In the developer console, choose the app you want to share. * Select Distribution in the left menu, and under…

Hi Jan, What code snippet are you using to store and retrieve the data? And what error are you getting? Thanks Wendy