Bitbucket Deployment Notification and Changelog

Overview

This flow auto-generates and distributes deployment release notes from Bitbucket. When code is pushed to a configured deployment branch (e.g. main, release, production), it compiles the commits in that push into a changelog, archives the changelog as a Markdown file in a SharePoint release-notes library, posts a summary to a Teams release channel, and emails the changelog to stakeholders via Outlook.

Why it matters: Hand-written changelogs get skipped under deadline pressure. Generating them automatically from the push commit set keeps developers, operations, and stakeholders informed of exactly what shipped — with zero manual effort.

As-built status: Solution created, flow published in the Off state, Flow Checker 0 errors / 0 warnings. Going live requires only connection authorization, environment-variable values, and registering the Bitbucket repo webhook (auto-registered when the flow is turned On).

Use Case

A development / release team wants automatic, distributed release notes whenever a deployment lands on a protected branch. Audience: Developers and Operations.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Bitbucket	shared_bitbucket	CreateHookRepositoryPush
SharePoint	shared_sharepointonline	CreateFile
Microsoft Teams	shared_teams	PostMessageToConversation
Office 365 Outlook	shared_office365	SendEmailV2

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Deployment branches

Edit flowlibs_DeploymentBranches to match your branching model (e.g. release/* patterns can be matched by expanding the condition logic).

Conventional commits

Extend Append_Markdown_Line / Append_HTML_Line to group commits by feat: / fix: / chore: prefixes.

Ticket links

Parse Jira/issue keys from commit messages and hyperlink them in the changelog.

Archive format

Change the file extension/body in Compose_Release_Notes_Document + Create_Release_Notes_File to produce HTML or .txt notes, or point at a different library via flowlibs_ReleaseNotesFolderPath.

Recipients & channel

Repoint flowlibs_ReleaseStakeholderEmails, flowlibs_TeamsGroupId, flowlibs_TeamsChannelId.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

@coalesce(first(triggerBody()?['push']?['changes'])?['new']?['name'],'')

@contains(split(toLower(variables('varDeployBranches')),','), toLower(outputs('Compose_Pushed_Branch')))

@coalesce(items('Apply_To_Each_Commit')?['author']?['user']?['display_name'], items('Apply_To_Each_Commit')?['author']?['raw'], 'Unknown')

@{concat(parameters('EnvVar_BitbucketRepoSlug'),'-',outputs('Compose_Pushed_Branch'),'-',formatDateTime(utcNow(),'yyyyMMdd-HHmmss'),'.md')}

Customize & download