Bug report

Describe the bug

As best as I can tell, the documentation at https://nextjs.org/docs/advanced-features/debugging only describes how to configure debugging for the node process in vscode. It doesn't provide any specific instructions on how to debug code that is run in browser, in chrome at the client side.

I think this is problematic because (speaking for myself) most

Summary

Where: https://www.gatsbyjs.org/docs/ssr-apis/#onRenderBody

What: Improve the example for onRenderBody or add another example, simple, that is not tied to a plugin.

Suggestion

// Object of props
const HtmlAttributes = {
  "data-whatever": "content"
}

// Magic
exports.onRenderBody = (
  { setHtmlAttributes }
) => {
   setHtmlAttributes(HtmlAttributes)
}

请不要直接在 issues 提交安全漏洞报告，目前已有一部分人正在使用该系统，你的公开提交很可能影响到他们的资料安全。

所以拜托以后直接发送安全漏洞信息到 hi@halo.run 谢谢！

Describe the bug

GitHub provides a few options when configuring a new repo like: license, .gitignore file, a README.md, and the Rennovate plugin. If you want to install any of these by default, which I usually do, then you get an error about the remote having newer content.

To Reproduce
Steps to reproduce the behavior:

1. Create a repo with a readme during the script
2. See the er