[bot] Sync Copilot Workshops: app first-steps Pages lesson + Korean landing

[github-actions]

What changed upstream

Compared github-samples/copilot-workshops@main (bb048c5) against the last sync (aeebea5):

• #200: First steps Copilot app gains new Lesson 12 – Deploy the site with GitHub Pages; review lesson renamed to 13; Lesson 3 reworked (project/usage details); Lesson 11 next-link updated; 3 SVGs added/updated. Applied to all 5 locales (translated 12 only exists for ko-kr upstream).
• #201: Korean real-world localization + a minor edit to docs/ko-kr/README.md, plus small English edits in real-world CLI/VS Code/cloud pages.

What was updated locally

• English + es-es/ja-jp/ko-kr/pt-br/zh-cn first-steps/copilot-app/: index.md, 3-inspect-and-test.md, 11-canvas.md, 12-review.md → 13-review.md (renamed).
• English + ko-kr: new 12-deploy-pages.md (other locales fall back to English via Astro).
• ko-kr/.../copilot-workshops/index.md synced from upstream.
• Images: added first-steps-app-pages-deploy.svg, updated first-steps-app-project-details.svg and first-steps-app-usage-details.svg.
• website/astro.config.mjs: redirect first-steps/copilot-app/12-review/ → 13-review/ for all locales.

Deferred (not in this PR)

• Real-world CLI restructure (new lessons 2–10 ordering) in English and ko-kr, small English edits in CLI/VS Code/cloud pages, and the full ko-kr real-world VS Code / cloud / CLI / overview translations. These are large and need their own run (including hasTranslations and redirect updates), so the sync baseline for these harnesses is not advanced.

Validation

npm run website:build could not run (missing js-yaml dependency in the sandbox); local links and image paths were checked with a script (only non-ko locale links to 12-deploy-pages rely on Astro English fallback).

Source

https://github.com/github-samples/copilot-workshops/commits/main

The markdown body of this workflow can be edited directly on GitHub.com without recompilation.

Warning

Firewall blocked 2 domains

The following domains were blocked by the firewall during workflow execution:

• api.github.com
• raw.githubusercontent.com

[!TIP]
api.github.com is blocked because GitHub API access uses the built-in GitHub tools by default. Instead of adding api.github.com to network.allowed, use tools.github.mode: gh-proxy for direct pre-authenticated GitHub CLI access without requiring network access to api.github.com:

tools:
  github:
    mode: gh-proxy

See GitHub Tools for more information on gh-proxy mode.

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "api.github.com"
    - "raw.githubusercontent.com"

See Network Configuration for more information.

Generated by Copilot Workshops Content Sync · copilot · auto · 58.2 AIC · ⌖ 1.1 AIC · ⊞ 16.7K · ◷

[github-actions]

🚦 Submission status: ⏳ Awaiting automation

Risk tier: merge-risk:medium — New or substantially changed resource without privileged execution
Required to merge: passing submission-gate checks plus 1 approval from reviewers with write access.

Why this tier

• Adds 5 file(s), e.g. website/public/images/learning-hub/copilot-workshops/first-steps-app-pages-deploy.svg
• Removes or renames files
• Changes 711 lines (low-risk limit is 40)

Automated checks

Check	Status	Details
Line endings	🔧 Infrastructure failure	Waiting for a maintainer to approve workflow runs for this PR · logs
Spelling	🔧 Infrastructure failure	Waiting for a maintainer to approve workflow runs for this PR · logs
Contributor reputation	🔧 Infrastructure failure	Waiting for a maintainer to approve workflow runs for this PR · logs
Duplicate resource scan	⚠️ Failed (advisory, non-blocking)	Waiting for a maintainer to approve workflow runs for this PR · logs
PR quality signal	⚠️ Failed (advisory, non-blocking)	Waiting for a maintainer to approve workflow runs for this PR · logs

Action needed

• 🔧 Line endings, Spelling, Contributor reputation hit an automation problem that is not caused by your contribution. Comment /rerun-checks to retry; maintainers are notified if it keeps failing.
• ⚠️ Advisory checks did not complete (Duplicate resource scan, PR quality signal). This does not block the PR.

Review

• Approvals: 0/1
• Assigned reviewer: not assigned yet — comment /request-review to ask for one
• Review target date: not set
• Still needed: 1 more approval(s)
• No staffed reviewer pool owns these files yet; any reviewer with write access counts as the domain reviewer.

Commands

Command	Who	What it does
/rerun-checks	PR author, maintainers	Re-runs failed or incomplete checks and re-evaluates this gate
/request-review	PR author, maintainers	Asks the review rotation to assign a reviewer (adds needs-reviewer)

_{Updated for 110997f · gate run · This comment is maintained automatically — see submission gate docs.}