# Ondes PRO and GitHub: your website, straight from your repo > Host a GitHub repository’s static site on Ondes PRO, redeployed on every git push, or let an AI agent add your online store to your existing website’s code. Updated on 2026-10-21 · The Ondes PRO team · https://ondes.pro/en/integrations/github Does your website already live in a **GitHub** repository? Ondes PRO uses it in two ways. It can **host that repository’s static site** on your Ondes PRO address and put it back online on every `git push`. And it can **connect your existing site to the store**: an AI agent builds the catalogue and checkout into your code, asks its questions first, and commits or publishes nothing without your say-so. ## Host a GitHub static site on Ondes PRO From the Website module in your admin, in a few minutes. 1. **Pick GitHub as the source** — In **Website**, create a site and choose the GitHub source, alongside the built-in builder and Ondes GIT. 2. **Connect your GitHub account** — Authorisation goes through the Ondes PRO platform, so the GitHub app secret is never copied into your workspace. If you already connected GitHub for the store, the same account is reused. 3. **Choose the repository, branch and folder** — Only repositories you can push to are offered. Set the branch to publish and, if needed, the subfolder holding the already-built site. 4. **Read the diagnosis, then publish** — Ondes PRO inspects the repository and warns you if it finds no `index.html`, or if it spots a tool that needs a build step. It then suggests any publishing branches it found. 5. **Push, and it is live** — A webhook dedicated to this site is added to the repository: every `git push` to the chosen branch redeploys the site. You can still resync by hand at any time. ## A redeploy on every git push, with no downtime - **No exposed `.git` folder**: Ondes PRO downloads an archive of the repository rather than cloning it into the public folder. - **A swap, not a rewrite**: the new version is prepared alongside, then switched in one move. A failed import leaves the previous version online. - **The archive is treated as untrusted input**: symlinks ignored, paths checked, size capped both when downloading and when unpacking. - **One secret per site**: one repository’s webhook cannot redeploy another site in your workspace. - **Private repositories** work, since access goes through your GitHub account. ## Connect my site: add the store to an existing website Plenty of merchants have a site they love and no wish to rebuild it. The **My site** tab of the Store & Orders module connects that site’s repository, on GitHub or in Ondes GIT, and hands the job to an AI agent: list your products, add a basket, wire up your store’s [Stripe](https://ondes.pro/en/integrations/stripe) checkout. The agent works on a copy of the repository. It reads and writes files but **runs no commands** and adds no dependencies; it relies on an integration contract derived from your store’s real routes, which keeps it from inventing an endpoint that would fail for your customers. The full walkthrough is in the [connect your website](https://ondes.pro/en/integrations/mcp/guides/connect-your-website) guide. ## The agent asks before it writes _Example conversation · demo data (Atelier Lumen)_ > **You** : Add a buy button to the Brass collection product pages. > > **Assistant** : I found the pages under `collection/laiton/`. One question before I write anything: should the basket open as a side panel on the same page, or lead to a dedicated “Basket” page? > > **You** : A side panel, like on the home page. > > **Assistant** : Got it. I changed four files and added Stripe’s payment script through a script tag. The diff is ready for review: nothing is committed or pushed to your repository until you click the button to approve the changes. > **Your repository stays under your control** — The GitHub token never appears in the repository’s Git config or on a command line. Pushes use the account of the person doing the work, never a colleague’s, and **never force-push**: if the branch moved in the meantime, the changes go to a fresh branch. Disconnecting GitHub revokes the authorisation on GitHub’s side. ## What if my code is not on GitHub? Ondes PRO also hosts Git repositories: **Ondes GIT**. It works as a source for both the Website module and “Connect my site”, with no third-party account. For a developer who would rather code everything, the [REST API](https://ondes.pro/en/integrations/rest-api) and the [MCP server](https://ondes.pro/en/integrations/mcp) reach the catalogue, orders and site pages. ## Go further - [Connect your website](https://ondes.pro/en/integrations/mcp/guides/connect-your-website) — Show the catalogue and take Stripe payments from a site that is already live, without rebuilding it. - [Web agencies and IT services](https://ondes.pro/en/integrations/mcp/industries/web-agencies) — One MCP server per client, documentation that is always accurate, and a test mode to ship without breakage. - [Online store](https://ondes.pro/en/integrations/mcp/modules/online-store) — Orders, catalogue, promo codes and shipments handled by your assistant, in test mode by default. - [Stripe](https://ondes.pro/en/integrations/stripe) — Take store payments into your own Stripe account, company by company. ## Frequently asked questions ### Can I host a Next.js, Astro or Vite site from GitHub? Yes, as long as the built output (the folder containing `index.html`) is in the repository, for example on a publishing branch or in a subfolder. Ondes PRO serves static files and runs no build step; the diagnosis warns you when it detects one. ### Does the site update automatically? Yes. Every `git push` to the chosen branch triggers a redeploy through a webhook. Pushes to other branches are ignored, and you can resync by hand. ### Are private repositories supported? Yes. Access goes through your GitHub account, connected via OAuth; only repositories you can push to are offered. ### Can the “Connect my site” agent break my site? It works on a copy and shows you a diff before anything is committed. Nothing reaches your repository without your click, never by force-push, and a rejection from GitHub leads to a fresh branch rather than overwriting your work. ### What happens if I delete the site in Ondes PRO? Its published files and images are erased, and the webhook on the GitHub repository is removed. Your repository itself is left untouched. ### Do I need a GitHub account for these features? For a GitHub source, yes. Otherwise Ondes GIT, included in Ondes PRO, plays the same role with no third-party account.