Release Change Digest to Teams

Overview

FlowLibs - Release Change Digest to Teams is a manual-trigger cloud flow that accepts a base and head ref (branch names or commit SHAs), calls the GitHub Compare Two Commits API, and posts a formatted HTML digest to a Microsoft Teams channel. The digest shows status, commit counts, ahead/behind counts, files-changed count, unique author names, and a direct link to the comparison on GitHub — ideal as release-notes pre-reading or a deploy sanity check.

Use Case

Before cutting a release, an engineering lead wants a one-click summary of everything that changed between two refs — typically main vs. a release branch, or the last deployed SHA vs. HEAD. Rather than clicking through the GitHub compare view, they run this flow with the two refs and receive a ready-to-share digest in the team's Teams channel.

The flow is ideal for teams that:

• Pre-release or pre-deploy sanity check from inside Teams.
• Generate share-ready release notes pre-reading without manual editing.
• Capture the unique author list across a range for callouts.
• Provide a one-click GitHub compare link directly inside the team channel.

Flow Architecture

Environment Variables

Connectors & Connections

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.

Change the target repository

Update flowlibs_GitHubOwner and flowlibs_GitHubRepository env vars.

Change the target Teams channel

Update flowlibs_TeamsGroupId and flowlibs_TeamsChannelId for the target environment.

Change the digest title

Edit the Init varDigestTitle action's value (e.g. 'Weekly Change Digest', 'Hotfix Diff').

Include file list

Extend Compose_Digest_Message_HTML with a Select over body('Compare_Commits_In_GitHub')?['files'] and render filename, status, additions/deletions.

Adaptive card instead of HTML

Swap PostMessageToConversation for Teams' Post Adaptive Card action and map the same fields.

Schedule it

Replace the manual trigger with a Recurrence trigger to post a daily/weekly digest against two fixed refs.

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(body('Compare_Commits_In_GitHub')?['commits'], json('[]'))

if(empty(body('Select_Author_Names')), 'n/a', replace(replace(replace(replace(string(body('Select_Author_Names')), '"},{"name":"', ', '), '[{"name":"', ''), '"}]', ''), '"name":null', 'unknown'))

length(coalesce(body('Compare_Commits_In_GitHub')?['files'], json('[]')))

body('Compare_Commits_In_GitHub')?['html_url']