Use the repository and branch holding the intended production project, not an editor workspace or an unrelated parent directory.
Documentation
Connect a GitHub repository.
GitHub is the connected source route for Host Luma AI Hosting. Connect the repository containing the production project you have already checked.
Before connecting
Confirm what you are going to deploy.
Static releases produce finished browser files. Supported Node 22 web apps need npm start, the supplied PORT and GET /health.
Do not put passwords, private keys or service credentials into the repository. Ask support before assuming a connection supports a different access model.
Connection workflow
Give the Portal a specific, reviewable source.
Open the AI Hosting project and begin the GitHub connection from the application controls.
Complete the connection only for the repository access you understand and expect. Review the repository and branch before saving.
Choose Static site for finished files, or Node.js application only for the documented managed Node HTTP contract.
Use the deployment record and logs to verify the connection. Correct the source in GitHub instead of copying files to a server.
Repository boundaries
Keep private and organisation access deliberate.
Private repositories can use per-application deploy-key access when it has been configured and verified. Organisation-owned repository access needs the appropriate review and authorisation; it is not a blanket self-service promise. Contact support before relying on a repository move, rename, connection change or organisation setup.
Connecting GitHub does not add database hosting, Docker, PHP or arbitrary worker support. Read the framework compatibility reference before selecting a deployment type.