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

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

@hiromieguchi802-lab I'll ask for a technical review of this for accuracy, then do a quick once-over myself for obvious places to improve grammar and flow, and then kick it over to the docs team review board for a final edit. Just to prepare you, the only one of those steps that's typically fast is the second one, although sometimes we get surprised and get a quick turnaround on the rest.

A stale label has been added to this pull request because it has been open 30 days with no activity. If you think this pull request should remain open, please add a new comment.

A stale label has been added to this pull request because it has been open 30 days with no activity. If you think this pull request should remain open, please add a new comment.

Thanks for opening a pull request! We've triaged this issue for technical review by a subject matter expert 👀

This is a gentle reminder for the Technical Content team that this PR is waiting for technical review by a subject matter expert.

A stale label has been added to this pull request because it has been open 30 days with no activity. If you think this pull request should remain open, please add a new comment.