Pull Requests Tagging

June 19, 2026 ยท View on GitHub

If you need to tag folks on an issue or PR, you will generally want to tag the owners (not the lead) for area to which the change or issue is closest to.

Areas

AreaLeadOwnersNotes
area-acquisition@joperezr@aspire/area-acquisitionIssues/PRs related to how Aspire is installed and acquired
area-app-model@adityamandaleeka@aspire/area-app-modelIssues/PRs related to the Aspire app model and Aspire AppHost
area-app-testing@ReubenBond@aspire/area-app-testingIssues/PRs related to the framework we provide for scenario testing of Aspire apps
area-integrations@sebastienros@aspire/area-integrationsIssues/PRs related to Aspire Integrations
area-dashboard@JakeRadMSFT@aspire/area-dashboardIssues/PRs related to the Dashboard UI
area-deployment@davidfowl@aspire/area-deploymentIssues/PRs related to deploying Aspire apps
area-docs@IEvangelist@aspire/area-docsIssues/PRs related to documentation
area-engineering-systems@joperezr@aspire/area-engineering-systemsIssues/PRs related to how the repository is built and tested (build and test infrastructure)
area-vscode-extension@adamint@adamintIssues/PRs related to the Aspire VS Code extension
area-meta@danmoseley@aspire/area-metaIssues/PRs that don't really match any of the other areas
area-orchestrator@dbreshears@aspire/area-orchestratorIssues/PRs related to DCP (Devex Control Plane)
area-samples@DamianEdwards@aspire/area-samplesIssues/PRs related to the Aspire samples. These are in the microsoft/aspire-samples repo.
area-service-discovery@ReubenBond@aspire/area-service-discoveryIssues/PRs related to Aspire's Service Discovery and communication between services
area-templates@DamianEdwards@aspire/area-templatesIssues/PRs related to the Aspire templates
area-telemetry@maddymontaquila@aspire/area-telemetryIssues/PRs related to telemetry (logs, metrics, tracing)
area-tooling@JakeRadMSFT@aspire/area-toolingIssues/PRs related to Visual Studio and Visual Studio Code tooling for Aspire

Community Triagers

While not necessarily associated with a specific area, these community members have the power to assist with routing and fixing labels of issues and pull requests, and are generally knowledgeable about how the repo works:

  • @Kahbazi
  • @Alirexaa
  • @davidebbo
  • @afscrome