Approval/review workflow + audit logging for Bitbucket-based Flow Registry Clients?

[#1]

Hi all — we're migrating from NiFi Registry to the git-based Flow Registry Client, specifically the BitbucketFlowRegistryClient (NiFi 2.11.0), and validating the workflow.

From what we've seen so far, committing a flow version via the NiFi UI pushes directly to the configured Bitbucket branch, with no built-in approval step — any review has to happen externally via a Bitbucket PR after the fact.

Questions for the community:

Approval workflow: Is there any NiFi-native mechanism (now or planned) to gate a version commit behind a review/approval, or is external git-host PR review the intended pattern?
Branching: For teams enforcing PR-based review on flow changes, do you commit to a feature branch by default and require manual PR creation, or is there tooling to automate opening the PR after a NiFi commit?
Diffing: Any recommended pattern for diffing flow JSON in PRs on Bitbucket specifically? We saw Datavolo's Flow Diff GitHub Action for GitHub — is there an equivalent for Bitbucket, or does anyone have a working setup?
Audit/logging: Beyond the git commit history (which only shows meaningful per-user attribution if using the "Application User" Commit Author Source), is there a recommended way to correlate NiFi's own Configuration History/Actions audit log with Bitbucket commit history, so we get a full picture of who changed what — both at the component level in NiFi and the version level in the repo?