Skip to main content
GitHub integration is optional — your Hiveku project works fine without it. But connecting a repo gives you real version history, branches for experimenting, pull requests for review, and a full backup outside Hiveku.

​
Connect a GitHub Repo

1

Open GitHub settings

In your project, go to Settings > GitHub and click Connect GitHub.
2

Authorize the Hiveku GitHub App

You’ll be redirected to GitHub. Choose whether to install the app on your personal account or an organization, and which repos to grant access to.
“All repositories” is convenient but “Only select repositories” is safer if you work across multiple projects.
3

Pick or create a repo

Back in Hiveku, choose:
  • Existing repo — pick from the list
  • New repo — Hiveku creates a fresh repo under the account or org you installed on
4

Initial push

Hiveku does an initial commit with every file in your project and pushes it to the main branch. From this point on, the repo and your project stay in sync.

​
Commit Changes

You’ve got three ways to commit, pick whichever fits the moment.
Open the GitHub panel in the editor (right sidebar). You’ll see a list of changed files.
  • Review the diff by clicking a file
  • Write a commit message in the input
  • Click Commit to commit to the current branch
  • Click Push to push to GitHub

​
Branches

From the GitHub panel in the editor:
  • Switch branch — click the current branch name and pick another
  • Create branch — click New branch, name it, choose base branch
  • Merge — open a PR from the panel and merge in GitHub
  • Delete — right-click a branch in the list
Branches are a great way to experiment. Create a feature/new-hero branch, try a redesign, and either merge it back or throw it away — without affecting your live site.

​
Pulling Remote Changes

If you or a teammate edited files directly on GitHub (or in another Hiveku instance), pull them into your local project.
1

Commit first

Pulling can overwrite unsaved local changes. Commit everything you want to keep first.
2

Click Pull

In the GitHub panel, click Pull. Hiveku fetches the remote and merges into your current branch.
3

Resolve conflicts if any

If the same file was edited both locally and remotely, you’ll see a conflict. The AI can help: “Resolve the merge conflict in src/page.tsx”.

​
Commit History and Pull Requests

From the GitHub panel:
  • History tab — scroll back through every commit with author, message, and timestamp
  • Pull Requests tab — view open PRs, preview the diff, leave comments, merge when ready
Pull requests made in Hiveku appear on GitHub just like any other PR — they can use your existing review process, CI, and branch protection.

​
Verifying It Works

Open your repo on github.com. You should see:
  • All your project files in the file tree
  • Your initial commit in the commit history
  • A green status next to your account in Settings > GitHub in Hiveku

​
Troubleshooting

The Hiveku GitHub App may not be installed, or the install was removed. Go to github.com/settings/installations, check for Hiveku, and reinstall if missing. Then try Connect GitHub again.
Someone else pushed to the same branch. Resolve the conflict in GitHub’s web UI or ask the AI to help locally, then pull again.
A commit without a push only exists locally. Click Push in the GitHub panel. Also refresh github.com — browser caching sometimes shows stale state.
In Settings > GitHub, click Disconnect. Your project keeps working and the repo stays on GitHub — they just stop syncing. Reconnect any time.

​
What’s Next?

GitHub Reference

Full reference: branch policies, PR settings, sync modes

Editor Git Panel

Deep dive on the in-editor Git controls