Built-in Git server
RBS includes an integrated Git server so you can host your code on the same platform that builds, tests, and deploys it. No separate Git hosting service required.
Why use the built-in Git server?
- Zero-config CI: pushes automatically trigger builds on the branch server.
- Branch = server: every active branch gets a dedicated build environment.
- Faster clones: your code is already on the platform — no network round-trip to clone.
- Unified access control: one set of permissions for code, builds, and deployments.
You can also import repositories from GitHub, GitLab, or Bitbucket if you prefer an external Git host. RBS mirrors the repository and keeps it in sync.
Getting started
Create a repository
From the RBS Dashboard:
- Click New Project → Create new repository.
- Name your repository and choose visibility (public or private).
- Click Create.
Clone and push
# Clone the repository
git clone https://git.rbs.dev/your-org/your-repo.git
cd your-repo
# Create your project files
echo 'config_setting(key = "project_name", value = "my-app")' > WORKSPACE.rbs
# Push
git add -A
git commit -m "Initial commit"
git push origin main
Import an existing repository
# From the dashboard, choose "Import repository" and provide the URL
# Or use the CLI:
rbs project import --url https://github.com/your-org/your-repo.git
Branch-based servers
Every active branch in your repository can have a dedicated RBS server. The server starts automatically when:
- A developer connects to the branch from their editor.
- A push is made to the branch (for CI).
- A scheduled workflow runs on the branch.
Branch lifecycle
| Event | Server state |
|---|
| First push to new branch | Server created, repo cloned, workers deployed. |
| Developer connects via editor | Server starts (if not running). |
| Push to branch | CI workers execute workflows. |
| All users disconnect | Server idles (configurable auto-shutdown). |
| Branch merged or deleted | Server decommissioned, resources cleaned up. |
Working with branches
# Create and push a new branch
git checkout -b feature/user-auth
git push origin feature/user-auth
# → RBS creates a new server for this branch
# Switch branches in your editor
# → Your editor reconnects to the correct branch server
# Delete a branch
git push origin --delete feature/user-auth
# → RBS decommissions the branch server
Authentication
SSH keys
# Add your SSH key in the dashboard under Settings → SSH Keys
# Then clone with SSH:
git clone git@git.rbs.dev:your-org/your-repo.git
HTTPS with tokens
# Generate a personal access token in the dashboard
git clone https://your-token@git.rbs.dev/your-org/your-repo.git
# Or configure Git credential helper
git config credential.helper store
Access control
Manage who can access your repositories:
| Role | Read code | Write code | Manage settings | Manage members |
|---|
| Viewer | ✅ | ❌ | ❌ | ❌ |
| Developer | ✅ | ✅ | ❌ | ❌ |
| Maintainer | ✅ | ✅ | ✅ | ❌ |
| Admin | ✅ | ✅ | ✅ | ✅ |
Branch protection
Protect important branches from direct pushes:
Settings → Branches → Branch protection rules
main:
✅ Require pull request reviews (1 approval)
✅ Require all CI checks to pass
✅ Prevent force pushes
✅ Require agents to approve (optional)
Webhooks
Configure webhooks to notify external services:
| Event | Description |
|---|
push | Code pushed to any branch. |
pull_request | PR opened, updated, merged, or closed. |
build:completed | A build finished (success or failure). |
test:completed | Tests finished running. |
deploy:completed | A deployment finished. |
Settings → Webhooks → Add webhook
URL: https://your-service.com/hooks/rbs
Secret: ********
Events: push, pull_request, build:completed
Mirroring external repositories
If you host code on GitHub, GitLab, or Bitbucket, you can set up bidirectional mirroring:
- Go to Settings → Mirrors.
- Add the external repository URL.
- Configure sync direction:
- Pull mirror: RBS pulls from the external repo (read-only import).
- Push mirror: RBS pushes changes to the external repo.
- Bidirectional: Changes sync both ways.
# Example: mirror from GitHub
rbs project mirror --url https://github.com/your-org/repo.git --direction bidirectional
Git LFS support
Large files are supported via Git LFS:
# Track large files
git lfs track "*.bin" "*.model" "datasets/**"
# Push as usual — LFS files are stored on the RBS platform
git add .gitattributes
git commit -m "Track large files with LFS"
git push
