aemresafak/locawise

Localizes applications using locawise

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Maintainedlast commit Jul 12, 2025
License: MIT

Pinned Snippet

workflow.ymlSHA-pinned

uses: aemresafak/locawise-action@603ac7c2d3d3ac981a1a638a4c70dd71773b6e54 # v1

tags can be moved; commit SHAs can't. why a SHA?

Inputs

name	description	required	default
openai-api-key	OpenAI API key if you are using the GPT models	no	""
vertex-ai-service-account-key-base64	Vertex AI service account key in base64 format if you are using a model from Vertex AI	no	""
source-lang-code	The language code of your primary language file (e.g., en).	yes	—
file-name-pattern	How your language files are named. {language} is replaced by the language code (e.g., en, tr).	yes	—
target-lang-codes	A comma-separated list of language codes you want to translate into (e.g., es,fr,de).	yes	—
localization-root-path	Path to the directory containing your language files (relative to repo root).	no	""
context	Detailed instructions for the AI about your application, tone, style, and target audience.	no	""
glossary	Define specific terms and their required translations (YAML formatted string e.g., "term1: translation1\nterm2: translation2").	no	""
tone	A description of the desired tone (e.g., "Formal", "Playful", "Professional but friendly").	no	""
llm-model	The specific model name from the provider (e.g., gpt-4o, gemini-1.5-flash). If omitted, locawise will use a default.	no	""
llm-location	The geographic location or region for the LLM API endpoint, if applicable (e.g., for Vertex AI).	no	""

Outputs

name	description
vertex-ai-service-account-key	Decoded Vertex AI service account key