[vibhoraggarwal]

Adds the url to the published pages on the Actions UI of the workflow

[AlexanderLanin]

Do you have an example of what this will look like? e.g. screenshot
Does that imply that we need to establish github-pages environment for all repos?
That url will not point to the PR preview, but the general docs, so whats the point?

[MaximilianSoerenPollak]

Do you have an example of what this will look like? e.g. screenshot Does that imply that we need to establish github-pages environment for all repos? That url will not point to the PR preview, but the general docs, so whats the point?

Reiterating this point here.
Can you answer this question? @vibhoraggarwal @av-etas

[vibhoraggarwal]

Do you have an example of what this will look like? e.g. screenshot Does that imply that we need to establish github-pages environment for all repos? That url will not point to the PR preview, but the general docs, so whats the point?

Yes, it should publish the deployed URL in the summary with the current change.
Although this is a simple change it could not possibly be done by workflows calling this workflows as they do not have access to the output of deploy-page job (which is a part of this workflow).

Motivation: It makes it easier to see where the documentation gets deployed with the current workflow and the user does not have to find it themselves.

That url will not point to the PR preview, but the general docs, so whats the point?

If a PR or a feature triggers the workflow the url would be pointed to the link referring to that link

[Copilot]

🟡 Changes recommended

URL handling introduces shell injection risk and breaks preview links for legacy deployments.

Get a fresh assessment by requesting another Copilot review.

Pull request overview

Adds published documentation URLs to GitHub Actions output and PR comments.

Changes:

• Adds the deployment URL to the job summary.
• Uses the deployment output URL in preview comments.

File summaries

File	Description
.github/workflows/docs-publish.yml	Publishes deployment links in summaries and PR comments.

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 2
• Review effort level: Balanced

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[AlexanderLanin]

@vibhoraggarwal can you have a look at the suggestions? They look reasonable to me.

[vibhoraggarwal]

@AlexanderLanin Now, I am using those suggestions.

[Copilot]

Copilot review overview

🟡 Changes recommended

Legacy deployments omit the summary, and deployment URLs may be malformed when the base URL lacks a trailing slash.

Get a fresh assessment by requesting another Copilot review.

Review effort: Balanced
Findings: 1

Open (1)

• Show Actions summary for legacy deployments with canonical URL fallback · New

Resolved since last review (2)

• This interpolates the target folder directly into a privileged shell script. For non-PR deployments…
• In deployment_type: legacy, the deploy-pages step is skipped, so page_url is empty while this…

[AlexanderLanin]

New PR overview attempt: Please mark the PR as ready for review once AI feedback is commented OR fixed, and resolved.

[Copilot]

🟢 Approval recommended

The URL fallback covers legacy deployments and the resolved output is consistently reused.

0 open findings

1 resolved since last review

• Show Actions summary for legacy deployments with canonical URL fallback

🧠 Review effort: Balanced