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.
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.
Accepted, with one correction to the framing: the PAT was never exposed to fork PRs — GitHub withholds secrets from
pull_requestworkflows triggered from forks regardless of repo visibility, so the security half of this doesn't apply. What IS right is the noise half: a merged fork PR whose branch happened to match a translation prefix would start this job with an empty token and fail red on a merged PR. The head-repo check skips it instead — belt-and-braces plus noise elimination, worth having on a PAT-bearing workflow.Because this file mirrors the upstream template, the fix went everywhere at once rather than only here: the template (action-translation#130), both harness targets, the still-open python.zh-cn#187 (amended), and follow-up PRs on the four already-merged copies (this repo's is #18).