Auto-enable Pages on first deploy

[bmehta001]

Summary

• Pass enablement: true to actions/configure-pages@v5 so the Deploy documentation to GitHub Pages workflow provisions the Pages site on first run.

Why

The post-merge deploy job has been failing on every push to main with::

Error: Get Pages site failed. Please verify that the repository has Pages
enabled and configured to build using GitHub Actions, or consider exploring
the `enablement` parameter for this action.
Error: Not Found - https://docs.github.com/rest/pages/pages#get-a-apiname-pages-site

gh api repos/microsoft/cpp_client_telemetry/pages returns 404, which means GitHub Pages has never been provisioned for this repository. actions/configure-pages accepts an enablement parameter that asks the action to create the Pages site on first run; the workflow already grants the pages: write and id-token: write permissions it needs to do so.

Fallback

If the org-level GITHUB_TOKEN restrictions still prevent automatic provisioning, a repository admin only needs to flip Settings -> Pages -> Build and deployment -> Source to GitHub Actions once; subsequent deploys will then succeed without the failure.

Validation

• YAML parsed cleanly with python -c "import yaml; yaml.safe_load(open(...))"
• Diff is a two-line addition under the existing actions/configure-pages@v5 step

[Copilot]

Pull request overview

This PR updates the GitHub Pages deploy workflow to automatically provision/enable the repository’s Pages site on the first successful deployment, addressing current Get Pages site failed / 404 failures when Pages hasn’t been configured yet.

Changes:

• Pass enablement: true to actions/configure-pages@v5 in the deploy job so the action can auto-enable Pages on first run.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[lalitb]

Are you sure this will work? As per the Github docs - this option requires a token other than GITHUB_TOKEN to be provided.

[bmehta001]

You are correct — I misread the docs. actions/configure-pages requires administration:write (PAT or GitHub App) to provision the Pages site; with only GITHUB_TOKEN, enablement: true will still 403. So this two-line diff is effectively a no-op.

Two real paths:

1. Close this PR and have an admin flip Settings → Pages → Source: GitHub Actions once. One-time, no secret to maintain, cleanest.
2. Add a PAGES_DEPLOY_TOKEN repo secret with admin:write and pass it via with.token here.

I'd lean (1) unless we expect this workflow to be cloned to new repos. Which would you prefer? Happy to push (2) or close in favor of (1).