Use KREW bot identity for translation automation - #25
Draft
Jwaminju wants to merge 1 commit into
Draft
Conversation
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
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.
What changed
author: KREW.Hugging Face KREW Translation Bot.KREW_BOT_TOKENmust be owned by thehuggingfacekrewGitHub account because GitHub uses the token owner as the PR and comment author.Why
Translation PRs and automation comments should be represented by the shared KREW bot account instead of an individual maintainer. Generated blog posts should also consistently resolve to the KREW author profile.
Deployment requirement
After merge, replace the
KREW_BOT_TOKENActions secret inHugging-Face-KREW/hf-workflowwith a fine-grained token created byhuggingfacekrew. Code changes alone cannot change the GitHub API author; the token owner determines that identity.Validation
138 passedgit diff --checkpasses.