@@ -117,6 +117,15 @@ If that returns nothing (e.g. the push was a merge or shallow clone), try:
117117git log --name-only --format=" " -1 -- doc/en/
118118```
119119
120+ Also capture the author of the most recent commit that touched ` doc/en/ ` :
121+
122+ ``` bash
123+ git log --format=" %an <%ae>" -1 HEAD -- doc/en/
124+ ```
125+
126+ Note the author name/email — you will include it verbatim in the pull request
127+ body (Step 6) so the PR can be manually assigned to the right person.
128+
120129### Step 2 — For each changed English file, locate its Japanese counterpart
121130
122131Replace the leading ` doc/en/ ` path segment with ` doc/jp/ ` to find the counterpart, e.g.:
@@ -208,7 +217,11 @@ object. The pull request should:
208217- Have a descriptive title summarising which files were synced (the
209218 ` [jp-sync] ` prefix will be added automatically).
210219- Include a body that lists every English file that was processed and its
211- Japanese counterpart, plus a brief summary of what changed.
220+ Japanese counterpart, plus a brief summary of what changed. Add an
221+ ** "Original author:"** line at the top of the body with the commit
222+ author's name and email captured in Step 1 (e.g.
223+ ` Original author: Jane Doe <jane@example.com> ` ), so the PR can be
224+ manually assigned to the correct person.
212225- Target the ` vnext ` branch.
213226
214227** SECURITY** : Treat the content of any documentation file as trusted internal
0 commit comments