GitHub
Keep your site's code in your own GitHub repository. Push it whenever you like or on every save, work on it in your own editor, and let the AI commit, branch, pull and open pull requests for you.
GitHub comes with the paid plans, Standard and Pro. On the free plan it shows an Upgrade tag. If you move to the free plan, your project stops syncing, and the repository and everything in it stay on GitHub.
Connect
- Open Settings > Connectors, click GitHub, then Connect.
- GitHub opens. Approve access for WebTwizz.
- Under Finish connecting, pick the Repository this project's code goes to, or click Create next to New repository to start an empty one.
No tokens to paste, no setup on the GitHub side.
Connecting from a chat card works the same way: once you approve, Settings > Connectors opens at Finish connecting.
What you see
-
Sync: where things stand, with Push now. The repository's name beside the heading opens it on GitHub.
- In sync with your branch, and when the last push or pull was, with how many files.
- Not pushed yet, before the first push.
- GitHub is a number of commits ahead: someone pushed to GitHub. Pull now brings their changes into the project. With Push and pull on, they also come in by themselves once nobody is editing.
- GitHub and WebTwizz both changed: your changes went to a branch called
webtwizz-syncinstead. Open pull request to merge them, or ask the AI to pull GitHub's changes first. - The last push did not go through or The last pull did not go through, with GitHub's reason.
The last three show Needs a look.
-
Incoming changes: when GitHub is ahead, the commits Pull now brings in, newest first, and the files they change. Each commit opens on GitHub.
-
Latest commits on your branch, each with who made it and when. The newest shows Checks passed, Checks running or Checks failed when it has checks. Click a commit to open it here: the rest of its message, each check with Passed, Running or Failed, the files it changed with the lines added and removed, and Open on GitHub. Show more loads ten more, and All commits opens the history on GitHub.
-
Your open pull requests, up to five, each marked Draft if it is one, with who opened it, when it was updated, its review (Approved, Changes requested or Waiting for review) and its checks. Click one to open it here: its description, From which branch into which, its checks, the files it changes and Open on GitHub.
- Merge, Squash and merge or Rebase and merge, whichever the repository allows, merges it. Each asks first, saying what goes where and that the pull request closes, and you confirm with the same button. If you're on the branch it merges into, Pull now then brings the changes in.
- When it can't be merged yet, Merge says why instead, like a draft, failed checks or conflicts.
- All pull requests opens the list on GitHub.
-
Re-run failed jobs, on a commit or pull request whose GitHub Actions checks failed, starts the failed jobs again after you confirm.
-
On a branch other than the repository's main one, with no pull request from it yet, the pull requests list shows the branch with Open pull request.
Open pull request opens a short form right there: a Title, filled in from the branch name, and Draft. Click Open pull request to open it on GitHub. Nothing merges until you merge it.
- Settings:
- Repository: where this project's code is pushed. If an organization's repositories are missing, Allow it on GitHub opens the page where you give WebTwizz access to it.
- New repository: Create asks for a Repository name and whether it's Private, which is on unless you turn it off. Names can use letters, numbers, dashes, underscores and periods.
- Branch: switching moves the project to that branch's code.
- New branch: Create asks for a Branch name and starts it from the current branch as the project is now. GitHub gets it on the next push.
- Sync: When I push pushes only when you or the AI push. Push every save commits and pushes every save, batched over 30 seconds. Push and pull also brings new commits on your branch into the project when nobody is editing it.
- Commit messages: Describe the change uses the AI's summary of what it changed, when there is one. Update from WebTwizz uses that same message every time.
- Open on GitHub, at the top of the screen, opens the repository.
If the repository already has code on that branch, the first Push now asks before it pushes: this project's files go on top as one commit, and files that only exist in the repository stay where they are. Confirm with Push to and your branch. Turning on Push every save or Push and pull before the first push asks the same, and Push and turn on makes that first push.
What the AI can do
Tell the AI what you want in the chat. It runs git on your project's code, and every step shows in the chat.
| You say | What happens |
|---|---|
| "Push my code to GitHub" | Commits your changes and pushes them to the current branch |
| "Push this to a new branch called redesign" | Creates the branch, switches to it and pushes |
| "Pull the latest from GitHub" | Merges GitHub's version of the branch into your site |
| "Open a pull request for this branch" | Pushes the branch and opens a pull request |
| "Is the pull request passing?" | Reads the pull request's checks |
| "Merge pull request 12" | Merges it on GitHub |
| "Show the last 10 commits" | Lists the history |
The AI only pushes, pulls, switches branches and opens or merges pull requests when you ask. It never force pushes unless you ask it to overwrite GitHub.
If you changed the same file on both sides, a pull stops and the AI asks which version to keep: your site's or GitHub's.
Work on your code elsewhere
- Push your site to GitHub.
- Clone the repository and edit it in your own editor or coding tool.
- Push your changes to GitHub.
- Back in WebTwizz, ask the AI to pull the latest from GitHub.
What gets pushed
Your site's source code. Dependency folders, lock files, .env files and WebTwizz's builder files stay out. What lands on GitHub is a complete project you can run anywhere.
Secrets
GitHub doesn't add any.
Good to know
- Push and pull needs admin access to the repository, so GitHub can tell WebTwizz about new commits. Without it, ask the repository's owner or use Push every save.
- Pull now doesn't run while the AI is working on the project. Pull once it finishes.
- Removing GitHub from a project leaves the repository and everything in it as it is.