How does the action talk to Azure?
Binyuze mu @azure-rest/ai-translation-text SDK ya Microsoft, yashyizweho @azure/core-rest-pipeline. Ibyo biguha ibisubizo byikora kuri 408/429/5xx, kwandika ubusabe n'ibisubizo by'ibisubizo, no gufata umutwe wo kwemeza ku buntu - ibintu byose byahoze ari guhamagara axios intoki. Ibicuruzwa by'ibicuruzwa (ibicuruzwa, ibicuruzwa, ibicuruzwa) ntibihinduka.
Kuki rimwe na rimwe abahinduzi bakunze gusesengura cyangwa gusezerana imbere y'amategeko?
Porogaramu ya USU ikora sisitemu yo kugenzura ibaruramari ryububiko bwibicuruzwa. 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.
Ni gute nakwirinda gusemura dosiye imwe inshuro ebyiri?
Kora igenzura ry'imikoreshereze y'ibicuruzwa by'ibicuruzwa by'paths by'umwihariko ibicuruzwa byawe, urugero nk'**/*.en.resx. The action also includes its own per-trigger file filter when GITHUB_TOKEN is set, narrowing work to files in the latest commit.
Nshobora gukora ibikorwa hanze ya interineti?
Not exactly — Azure AI Translator is the runtime brain. Ariko urashobora gukora hamwe na dryRun: true kugirango wemeze parsing na config utiriwe utanga ubusabe bwa HTTP bwo guhindura.
What Node version does the action run on?
v3 runs on the GitHub Actions node24 runtime. JavaScript ihuriweho na Node 20, 22, na 24, nibyo CI igerageza.
Izo dist/ z'amabuye y'agaciro zituruka he?
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.
Bite se ku bindi bikoresho by'ikoranabuhanga?
Uyu munsi: .resx, .xliff, .po, .json, .ini, .restext. Fungura ikibazo if you need another — the parser interface is small (parse → map → apply translations → format) and contributions are welcome.