You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Constrain the Translation Polisher to emit each safe output type at most once and require exact managed PR-body markers so safe output validation can complete.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copy file name to clipboardExpand all lines: .github/workflows/translation-polisher.md
+13-2Lines changed: 13 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -129,6 +129,17 @@ Do not edit:
129
129
15. Add the `translation-polished` label only when every changed target-language file is A- or higher.
130
130
16. Add a short pull request comment summarizing what was polished, which languages were touched, and the final grade range.
131
131
132
+
## Safe output limits
133
+
134
+
Emit each safe output type at most once:
135
+
136
+
- At most one `push_to_pull_request_branch`.
137
+
- At most one `update_pull_request`.
138
+
- At most one `add_labels`.
139
+
- At most one `add_comment`.
140
+
141
+
Do not emit duplicate label or comment requests. If a label is already present, do not emit an `add_labels` request for it. If you need to report both a quality summary and polishing summary, combine them into the single allowed pull request comment.
142
+
132
143
## Quality checklist
133
144
134
145
For every translated Markdown file you edit:
@@ -207,7 +218,7 @@ Apply the profile only when that language is present in the pull request.
207
218
208
219
## Pull request body update
209
220
210
-
After the final review, update the pull request body with a managed translation-quality section. Replace only the managed block between these markers:
221
+
After the final review, update the pull request body with a managed translation-quality section. Replace only the managed block between these exact lowercase markers:
211
222
212
223
```markdown
213
224
<!-- translation-quality-review:start -->
@@ -220,7 +231,7 @@ The body must include exactly one managed block and exactly one section inside t
220
231
## Translation Quality Review
221
232
```
222
233
223
-
If an older unmarked `## Translation Quality Review` section already exists, replace it with the marked block. Do not append duplicates. Do not place generated workflow footers, integrity notes, or unrelated comments inside the managed block.
234
+
If an older unmarked `## Translation Quality Review` section already exists, replace it with the marked block. Do not append duplicates. Do not change the marker casing. Do not place generated workflow footers, integrity notes, or unrelated comments inside the managed block.
0 commit comments