New story in the user guide. Target is the `main` branch of che-docs but it's expected to be published as a "minimalistic" Che blog article first (in AsciiDoc, using the same variables used in Che documentation and the same Vale rules).

Che helps reviewing GitHub pull requests. This article should explain:

How a maintainer of a project can setup his project to use Che

• Choose to deploy Che on a Kubernetes cluster or use Red Hat Developer Sandbox
• Add the GitHub action to the project
• If not using Developer Sandbox, customize the GitHub action to point to the Che instance
• Add a .devfile.yaml at the root of the project to customize components and commands
• Add a .vscode/extensions.json at the root of the project to include some VS Code extensions in Theia or VS Code based workspaces
• Add a .che/che-theia-plugins.yaml or .che/che-editor.yaml to customize it even further