#2392 AL-Go Telemetry Enhancements: repository fork and hosting information
AL-Go telemetry now captures whether a repository is a fork and its GitHub hosting type (GitHub.com, GHEC, or GHES), helping distinguish workflows across different environments without sending server details to telemetry.
- 5files
- 2AL files
- 0objects
Pull request · merged into main on 2026-10-07 by aholstrup1 · 5 files (+316 -0), 2 AL · feature · tier official · reviewed (checked by Opus)
What changed
- New
Get-RepositoryIsForkfunction determines fork status from workflow event metadata - New
Get-GitHubHostingTypefunction classifies GitHub hosting as GitHub.com, GHEC, or GHES - Telemetry dimensions include repository and hosting context for Microsoft and partner systems
- Invalid or missing metadata produces warnings and returns ‘Unknown’ without blocking telemetry
- Added 27 unit tests covering both PowerShell 7 and Windows PowerShell 5 compatibility
- Behaviour changes for users or extensions.
AL objects touched
Actions/Invoke-AlGoAction.ps1: modified, not in the BC? snapshotActions/TelemetryHelper.psm1: modified, not in the BC? snapshot
Context
- Systems: development, platform
- From the description: “Add repository and hosting context to AL-Go telemetry so consumers can distinguish workflows running in forks and across GitHub hosting environments.”
Source: metadata of a merged pull request in microsoft/AL-Go (al-go): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).