chore: fix Node.js TOC for cloud-rad

[fhinkel]

No description provided.

[bcoe]

I think this will result in 100 PRs without context tomorrow morning, due to landing this on the same day.

@SurferJeffAtGoogle any advice to make this less of a pain?

[SurferJeffAtGoogle]

They'll have context, but because there will be two commits in the PR, the PR title will be "Changes due to synthtool," yadayada. If you'd like to avoid that, visit fusion and trigger all 10 nodejs shards to rebuild. Merge the generated PRs, then merge this PR.

…

On Wed, Oct 21, 2020 at 7:45 AM Benjamin E. Coe ***@***.***> wrote: I think this will result in 100 PRs without context tomorrow morning, due to landing this <f96d3b4> on the same day. @SurferJeffAtGoogle <https://github.com/SurferJeffAtGoogle> any advice to make this less of a pain? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#822 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACZ3TYRE5MKMVLY22IMQYZ3SL3XZLANCNFSM4SZ4ATVA> .

[fhinkel]

Or we can wait a few days before we merge this? Sorry for the confusion. Of course I don't get a sed regex right on the first try.

[bcoe]

@SurferJeffAtGoogle @fhinkel why don't we just make sure at the end of the day today, that there are no PRs open with the title "Changes due to synthtool".

Then we can merge this, and tomorrow morning rename all the PRs?

[SurferJeffAtGoogle]

That's fine too. But clicking all the jobs in fusion is pretty easy: 2 clicks for each shard, and it's done. And it's no different from a nightly run.

…

On Wed, Oct 21, 2020 at 8:03 AM Benjamin E. Coe ***@***.***> wrote: @SurferJeffAtGoogle <https://github.com/SurferJeffAtGoogle> @fhinkel <https://github.com/fhinkel> why don't we just make sure at the end of the day today, that there are no PRs open with the title "Changes due to synthtool". Then we can merge this, and tomorrow morning rename all the PRs? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#822 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACZ3TYT2UAYVNKF5COXZGWTSL3Z3PANCNFSM4SZ4ATVA> .