Step 1: Kutoa rasilimali ya Mtafsiri wa Azure AI
Unda rasilimali ya Mtafsiri wa Azure AI kwenye lango la Azure, kisha uhifadhi yafuatayo kama siri za hazina ya GitHub ili mtiririko wa kazi uweze kuzisoma:
-
TRANSLATOR_KEY— ufunguo wa usajili wa rasilimali. -
TRANSLATOR_ENDPOINT— URL ya mwisho ya mkoa. -
TRANSLATOR_REGION— mkoa wa Azure wa rasilimali.
Step 2: Ongeza mtiririko wa kazi
Unda .github/workflows/translate.yml:
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: sourceLocale: en subscriptionKey: ${{ secrets.TRANSLATOR_KEY }} endpoint: ${{ secrets.TRANSLATOR_ENDPOINT }} region: ${{ secrets.TRANSLATOR_REGION }} 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: Fanya faili ya rasilimali ya chanzo
Faili za rasilimali hutumia mkataba wa Name.<sourceLocale>.<ext>. Kwa mfano Greetings.en.resx inakuwa Greetings.fr.resx, Greetings.de.resx, na kadhalika baada ya kukimbia.
Step 4: Kagua pato
Mara tu mtiririko wa kazi unapomalizika, kitendo kinafunua matokeo matatu unayoweza kuunganisha kwenye maelezo ya PR: summary-title, summary-details, na has-new-translations. Pia inaandika muhtasari wa Markdown kwenye ukurasa wa kazi kupitia core.summary.