Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions setup.ps1
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
Set-StrictMode -Version Latest
$ErrorActionPreference = "Stop"

Write-Host "`n=== Generative AI for Beginners .NET Automated Setup ===" -ForegroundColor Cyan
Write-Host "`n=== Generative AI for Beginners .NET - Automated Setup ===" -ForegroundColor Cyan
Copy link

Copilot AI Mar 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change replaces em dashes in output strings, but setup.ps1 still contains a non-ASCII em dash in the header comment (currently on line 2: "setup.ps1 — Automated setup..."). If Windows PowerShell is misreading non-ASCII characters due to file encoding, the parse issue may persist until that remaining em dash is also replaced (or the file encoding is adjusted consistently).

Copilot uses AI. Check for mistakes.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@copilot open a new pull request to apply changes based on this feedback


# --- Check prerequisites ---
foreach ($tool in @("azd", "dotnet")) {
Expand All @@ -17,7 +17,7 @@ foreach ($tool in @("azd", "dotnet")) {
if (Get-Command "az" -ErrorAction SilentlyContinue) {
Write-Host "Prerequisites OK (azd, dotnet, az)" -ForegroundColor Green
} else {
Write-Host "Prerequisites OK (azd, dotnet). 'az' CLI not found tenant detection will be skipped." -ForegroundColor Green
Write-Host "Prerequisites OK (azd, dotnet). 'az' CLI not found - tenant detection will be skipped." -ForegroundColor Green
}

# --- Deploy Azure infrastructure ---
Expand Down
Loading