Step 1: Wielt e Iwwersetzungsprovider
D'Aktioun funktionéiert mat Azure AI Translator, AWS Translate an Google Cloud Iwwersetzung hannert enger eenheetlecher API-Uewerfläch. Wielt pro Laf e eenzege Provider mat der provider Input — de Workflow funktionéiert identesch onofhängeg vum Provider; nëmmen d'Qualifikatiounen ënnerscheede sech. Kuckt Iwwersetzungsservicer fir e komplette Verglach.
Step 2: Füügt Zougangsdaten an e Workflow derbäi
Späichert d'Zougangsdaten vun Ärem Provider als GitHub-Repository-Geheimnisser a erstellt .github/workflows/translate.yml. Wielt Äre Provider hei drënner fir seng spezifesch Opstellung — de Rescht vum Workflow ass identesch.
Azure AI Translator
Azure ass de Standardprovider, dofir kann provider ausgelass ginn. Bereet eng Azure AI Translator Ressource am Azure Portal zur Verfügung a späichert dann hir Credentials:
Späichert dës als Repository-Geheimnisser
TRANSLATOR_KEY— de Abonnementschlëssel fir d'Ressource.TRANSLATOR_ENDPOINT— d'regional Endpunkt-URL.TRANSLATOR_REGION— d'Ressource ass d'Azure-Regioun.
Füügt de Workflow derbäi
name: translate
on: push: branches: [main] paths: - "src/**/*.en.resx" - "src/**/*.en.json"
permissions: contents: write pull-requests: write
jobs: translate: runs-on: ubuntu-latest steps: - uses: actions/checkout@v5 - id: translate uses: IEvangelist/resource-translator@v3 with: provider: | azure: subscriptionKey: ${{ secrets.TRANSLATOR_KEY }} endpoint: ${{ secrets.TRANSLATOR_ENDPOINT }} region: ${{ secrets.TRANSLATOR_REGION }} sourceLocale: en toLocales: '["fr","de","es"]' - if: steps.translate.outputs.has-new-translations == 'true' uses: peter-evans/create-pull-request@v7 with: title: ${{ steps.translate.outputs.summary-title }} body: ${{ steps.translate.outputs.summary-details }} branch: machine-translationAWS Translate
Setz provider op aws. Bevorzugt OIDC iwwer aws-actions/configure-aws-credentials, sou datt keng laangfristeg Geheimnisser gespäichert ginn — d'Schrëtt Exporten AWS_REGION fir Iech. Fir amplaz statesch Tasten ze benotzen, späichert:
Späichert dës als Repository-Geheimnisser
AWS_ACCESS_KEY_ID— Är AWS Access Key ID.AWS_SECRET_ACCESS_KEY— Ären AWS-Geheimzougangsschlëssel.
Eng Regioun ass ëmmer erfuerderlech — setzt se mat awsRegion oder der AWS_REGION Ëmweltvariabel.
Füügt de Workflow derbäi
name: translate
on: push: branches: [main] paths: - "src/**/*.en.resx" - "src/**/*.en.json"
permissions: id-token: write # for aws-actions/configure-aws-credentials (OIDC) contents: write pull-requests: write
jobs: translate: runs-on: ubuntu-latest steps: - uses: actions/checkout@v5 - uses: aws-actions/configure-aws-credentials@v4 with: role-to-assume: arn:aws:iam::123456789012:role/gh-actions-translate aws-region: us-east-1 - id: translate uses: IEvangelist/resource-translator@v3 with: provider: | aws: region: us-east-1 # or rely on AWS_REGION from the step above formality: FORMAL brevity: true sourceLocale: en toLocales: '["fr","de","es"]' - if: steps.translate.outputs.has-new-translations == 'true' uses: peter-evans/create-pull-request@v7 with: title: ${{ steps.translate.outputs.summary-title }} body: ${{ steps.translate.outputs.summary-details }} branch: machine-translationGoogle Cloud Iwwersetzung
Setz provider op google. Authentifizéiert Iech entweder mat engem Service-Kont JSON-Credential oder engem API-Schlëssel — liwwert genee een:
Späichert dës als Repository-Geheimnisser
GCP_TRANSLATE_CREDENTIALS— e Service-Kont JSON-Schlëssel (als JSON-String).GCP_TRANSLATE_API_KEY— oder e Google Cloud API-Schlëssel.
Eng optional googleProjectId gëtt aus der Qualifikatioun ofgeleet, wann se net ernimmt gëtt.
Füügt de Workflow derbäi
name: translate
on: push: branches: [main] paths: - "src/**/*.en.resx" - "src/**/*.en.json"
permissions: contents: write pull-requests: write
jobs: translate: runs-on: ubuntu-latest steps: - uses: actions/checkout@v5 - id: translate uses: IEvangelist/resource-translator@v3 with: provider: | google: # Provide EITHER a service-account JSON credential... credentials: ${{ secrets.GCP_TRANSLATE_CREDENTIALS }} # ...OR an API key: # apiKey: ${{ secrets.GCP_TRANSLATE_API_KEY }} model: nmt sourceLocale: en toLocales: '["fr","de","es"]' - if: steps.translate.outputs.has-new-translations == 'true' uses: peter-evans/create-pull-request@v7 with: title: ${{ steps.translate.outputs.summary-title }} body: ${{ steps.translate.outputs.summary-details }} branch: machine-translationStep 3: Commit eng Quellressourcedatei
Ressourcedateien benotzen d'Name.<sourceLocale>.<ext> Konventioun. Zum Beispill gëtt Greetings.en.resx no engem Laf Greetings.fr.resx, Greetings.de.resx, asw.
Step 4: Let smart change detection protect your bill
changeDetection defaults to smart and stores a compact .github/resource-translator-state.json manifest in the repo. Commit that file so future runs can reuse stable translations, preserve manual target edits, and send only new, missing, changed, or settings-invalidated keys to the provider. If localized files already exist, run once with snapshotOnly: true to create the manifest without provider calls.
Step 5: Iwwerpréift den Ausgang
Wann de Workflow fäerdeg ass, weist d'Aktioun dräi Outputen, déi s de an eng PR-Beschreiwung verbannen kanns: summary-title, summary-details an has-new-translations. Et schreift och eng Markdown-Zesummefaassung iwwer core.summary op d'Job-Säit.