Add Co-op Translator GitHub Action to branch-based push (no PR)#792
Merged
Conversation
Contributor
|
👋 Thanks for contributing @skytin1004! We will review the pull request and get back to you soon. |
leestott
approved these changes
May 23, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces a branch-based GitHub Action workflow for Co-op Translator, replacing the previous PR-based automation.
What's changed?
Instead of automatically creating a pull request, Co-op Translator now:
Pushes translation updates directly to the
update-translationsbranchSkips PR creation to avoid CLA (Contributor License Agreement) issues with GitHub Apps
Commits include the UTC date for traceability
(Commit ex:
🌐 Update translations on YYYY-MM-DD via Co-op Translator)Why this change?
GitHub App-generated PRs cannot pass the Microsoft CLA check, which blocks merges even for automated translation updates.
To ensure compliance while preserving automation, we’ve moved to a push-only model - contributors can manually open PRs from the update-translations branch when ready.
Workflow Overview
Below is a visual summary of the branch-based workflow: