Incorrect line breaks in zh-CN translation

[MDLZCOOL]

Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/zh/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors

What part(s) of the article would you like to see updated?

As we can see, there are incorrect line breaks.

Additional information

No response

[welcome]

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[Sharra-writes]

@MDLZCOOL I'm going to create a bug ticket for the translation team, and then when that's finished I'll close this issue. Thanks for bringing it to our attention!

[MDLZCOOL]

Hi @Sharra-writes, just checking in on this. I noticed the typo reported hasn't been addressed yet.

[Sharra-writes]

@MDLZCOOL So, theoretically, the translation team receives these issues as soon as I tag them with localization. That system has not always worked consistently in the past, though, so now, just to make sure, I file them as bugs in addition to tagging them. I usually wait until I have a batch, though, since the sign-on for filing them is multi-step and annoying. Theoretically the team already has this issue, and they just aren't that fast at making fixes. When I have a couple more of these issues, I will ensure that is the case by filing them all as bugs, and will then close them out.

If, after this is closed, you see it's been a month and it still isn't fixed, I'm fine with you opening another issue that will eventually be filed as another bug report. Pelting the translation team with bug reports until things get fixed sounds like a valid strategy.

[maliklife]

echo "{markdown content}" >> $GITHUB_STEP_SUMMARY

…

On Wed, Apr 1, 2026, 2:29 AM Sharra-writes ***@***.***> wrote: *Sharra-writes* left a comment (github/docs#43032) <#43032 (comment)> @MDLZCOOL <https://github.com/MDLZCOOL> So, theoretically, the translation team receives these issues as soon as I tag them with localization. That system has not always worked consistently in the past, though, so now, just to make sure, I file them as bugs in addition to tagging them. I usually wait until I have a batch, though, since the sign-on for filing them is multi-step and annoying. Theoretically the team already has this issue, and they just aren't that fast at making fixes. When I have a couple more of these issues, I will ensure that is the case by filing them all as bugs, and will then close them out. If, after this is closed, you see it's been a month and it still isn't fixed, I'm fine with you opening another issue that will eventually be filed as another bug report. Pelting the translation team with bug reports until things get fixed sounds like a valid strategy. — Reply to this email directly, view it on GitHub <#43032?email_source=notifications&email_token=B63ZM74RAF42A7JKVRO6MVL4TQ2DRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJWGU3DSNJQG432M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#issuecomment-4165695077>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B63ZM7YD2EIONF4FJACOPWL4TQ2DRAVCNFSM6AAAAACVUDBWQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCNRVGY4TKMBXG4> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Sharra-writes]

@MDLZCOOL Got this submitted as a bug, so I'm going to close it now. Thanks!