How to use GitHub Copilot to translate an Astro blog
Ago used Copilot issues and draft PRs to add English pages to an Astro blog, reviewing Azure authentication constraints before integrating the pipeline.
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Add English publishing to [Astro blog]. Plan separate routing, translation and SEO issues using [translation service]. Check [tenant permissions] and authentication before implementation. Return draft PRs with build results and generated-page examples for my review.
Reach people exploring AI agents
See placements →What happened
Memolog has translated /en/ pages and a GitHub Actions translation pipeline using Managed Identity.
Reported by Yoshitomo Ago (ag0u3) on BlogHow the agent did it
- Discussed SEO with local Agent Mode.
- Split routing, translation and SEO into issues.
- Cloud agent returned draft PRs.
Where a person stepped in
Author requested changes when tenant permissions blocked proposed authentication and decided merges.
Yoshitomo Ago used GitHub Copilot to add multilingual publishing to Memolog, an Astro blog hosted on Azure Static Web Apps. He first discussed international SEO with local Agent Mode and chose actual English HTML pages under /en/, rather than relying on browser translation.
Ago divided the work into issues covering multilingual routing, an Azure AI Translator pipeline and final SEO details such as canonical URLs, hreflang and the sitemap. Assigning the routing issue to the cloud coding agent produced a draft pull request while he worked elsewhere. Local Copilot then helped inspect the returned changes and validate them in his environment.
Authentication required human judgment. The translation PR initially proposed OIDC access from GitHub Actions, but Ago could not create an App Registration in his tenant. He requested changes to use working local AAD authentication and verified the build and generated English pages. Later evidence showed that a User Assigned Managed Identity with a federated credential could support OIDC, so the architecture changed again.
Memolog now runs translation through its own Managed Identity in GitHub Actions.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Blog · Yoshitomo Ago (ag0u3)
Frequently asked questions
Why generate separate English pages?
Ago wanted English-language search visibility. He chose translated HTML under /en/ because browser translation does not create indexable English pages.
How was the work delegated?
Routing, translation and SEO were separate GitHub issues; the cloud agent returned draft PRs and local Copilot assisted review and validation.
What authentication constraint changed the plan?
Ago could not create an App Registration. He first requested local AAD authentication, then adopted OIDC using a Managed Identity after finding workable tenant evidence.
More details
Remaining steps
- Local Copilot inspected diff and generated English pages; author revised authentication decisions.
About this account
Cloud Copilot implemented bounded translation/routing issues and returned draft PRs; local Copilot assisted diff review and build validation.
Primary first-person account opened and checked on 2026-10-14. Parallel issues also duplicated a homepage fix; operational constraints needed human judgment. Outcomes and test claims are attributed to the source and were not independently reproduced. Prompt is suggested by Agents In Use, not the author's quoted prompt.
Credit: Yoshitomo Ago (ag0u3) on Blog
Source published 31 Jul 2026
Source checked 14 Oct 2026
Tools and topics
GitHub Copilot · Astro · Azure AI Translator · GitHub Actions · Managed Identity
Multilingual blog · Astro · Azure
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.