How does the action talk to Azure?
Ka go diriša @azure-rest/ai-translation-text SDK ya semmušo ya Microsoft, e beakantšwe ka @azure/core-rest-pipeline. That gets you automatic retries on 408/429/5xx, typed request and response models, and authentication header handling for free — everything that used to be a hand-rolled axios call. Dipoelo tša ditšweletšwa (ditšweletšwa, ditšweletšwa, ditšweletšwa tša difaele) ga di fetoge.
Ke ka lebaka la eng ka dinako tše dingwe diphetolelo di sa fetoge?
Phetolelo ya motšhene e palelwa ke go fetolela ka kakaretšo. Three knobs help: a Glossary for hard term overrides, a Custom Translator category for fine-tuned models trained on your tone and vocabulary, and profanityAction to scrub or flag profane terms.
Nka efoga bjang go fetolela faele e tee gabedi?
Hlohleletša tshepedišo ya mošomo go paths tšeo di sepelelanago le difaele tša gago tša mothopo-locale fela, mohlala, **/*.en.resx. Tiro gape e akaretša filtara ya yona ya faele ya per-trigger ge GITHUB_TOKEN e beilwe, go fokotša mošomo go difaele tša commit ya moragorago.
Na nka dira tiro ya ka ntle ga inthanete?
Not exactly — Azure AI Translator is the runtime brain. Eupša o ka šoma le dryRun: true go kgonthišiša parsing le config ntle le go dira dikgopelo tša HTTP tša phetolelo.
What Node version does the action run on?
v3 Go Go Gadget Actions node24 Runtime JavaScript e sepelelana le Node 20, 22 le 24, e lego seo CI e se lekago.
O tšwa kae dist/ tše di tletšego?
GitHub JS actions ship their compiled JS in the repository. The dist-build workflow rebuilds it after every merge to main if it would drift, and dist-check blocks PRs that would land out-of-date output.
Go thwe'ng ka difomete tše dingwe tša methopo?
Lehono: .resx, .xliff, .po, .json, .ini, .restext. Bula taba if you need another — the parser interface is small (parse → map → apply translations → format) and contributions are welcome.