PR Title Normalizer

Overview

FlowLibs - PR Title Normalizer is a scheduled Power Automate cloud flow that polls a GitHub repository every 15 minutes for open pull requests and rewrites any PR title that does not start with an approved conventional-commits prefix (such as feat:, fix:, docs:). When the flow finds a non-compliant title it prepends the configured default prefix and posts an explanation comment on the PR so the author understands the edit.

The flow is a reference demo. It ships in the Off state with a GitHub connection reference and four environment variables — turning it on in any tenant is a matter of authenticating the GitHub connection, setting the env var values, and enabling the flow.

Use Case

Teams that enforce conventional-commits in their PR history often end up manually fixing sloppy titles at merge time. This flow automates the normalization so the Git log stays consistent without blocking contributors or adding a required CI check. Because it runs on a schedule it also retroactively fixes PRs that were opened while the flow was offline.

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.

Import the solution

Bring the solution into the target environment — managed for end users, unmanaged for builders who want to extend the logic.

Authenticate the GitHub connection reference

Bind the new_sharedgithub_1719c connection reference to a GitHub account that has write access to PRs in the target repository. This is the account whose token will rewrite titles and post the explanation comment.

Set the four environment variables

Configure flowlibs_GitHubOwner, flowlibs_GitHubRepository, flowlibs_PrValidPrefixes, and flowlibs_PrDefaultPrefix for the target repository, your team's approved prefix list, and the default prefix to apply when none matches.

Adjust the recurrence (optional)

Default is every 15 minutes. Increase the interval if your repo has low PR throughput to stay well under GitHub API rate limits.

Turn the flow On

The solution ships with the flow Off — enable it in the target environment once the connection reference and env vars are in place.

Optional extension: path-based prefix selection

Instead of a static flowlibs_PrDefaultPrefix, swap in logic that inspects the PR's changed file paths (e.g. docs/** → docs, test/** → test) before falling back to the default. Keep the valid-prefix check in place so titles that already comply are never rewritten.

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.

concat('is:pr is:open repo:', variables('varGitHubOwner'), '/', variables('varGitHubRepository'))

coalesce(body('Search_For_Open_Pull_Requests')?['items'], body('Search_For_Open_Pull_Requests'))

toLower(trim(first(split(outputs('Compose_Pr_Title'), ':'))))

and(contains(outputs('Compose_Pr_Title'), ':'), not(contains(split(variables('varValidPrefixes'), ','), outputs('Compose_Pr_First_Token'))))

concat(variables('varDefaultPrefix'), ': ', outputs('Compose_Pr_Title'))