-
Notifications
You must be signed in to change notification settings - Fork 3
Integrate Reusable Azure AI Translation Workflow from Central Repository #283
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
I don't see the |
@circlecube No, it has to be added on org level and I don't have permissions for the same. I have the key with me, but need help with adding it to org level. |
Co-authored-by: Jonathan Desrosiers <359867+desrosj@users.noreply.github.com>
Co-authored-by: Jonathan Desrosiers <359867+desrosj@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, @mr-vara! Just one thing missing here. Adding concurrency
will ensure that multiple workflows are not trying to create pull requests for the same branch at the same time.
Co-authored-by: Jonathan Desrosiers <359867+desrosj@users.noreply.github.com>
Proposed changes
This PR sets up the repository to use a centralized, reusable GitHub Actions workflow that automates localization file translation using Azure AI Translation (Microsoft Translator).
What’s Included
.po
and.json
files with optional context stripping.text_domain
, defaulting to the repository name if not provided.Configuration Notes
main
and via manualworkflow_dispatch
.TRANSLATOR_API_KEY
(Azure AI Translation)NEWFOLD_ACCESS_TOKEN
(for creating pull requests)This setup helps automate translation updates across repositories using a single, centralized translation logic.
Documentation
AI Translation Workflow Documentation