Inside Rezee - from push to production in one layer (Code & Ship)
The thinking behind Rezee's Code & Ship layer - standard git over HTTPS and SSH, inline pull request review, protected branches, and YAML pipelines with isolated steps and live logs.
Jul 30, 2026 · 3 min read · Kash Gohil
Rezee is one workspace for everything a team ships, organized as five layers. This post covers the one developers touch most: Code & Ship - git hosting, code review, and CI/CD. Its governing conviction: the code layer should be radically standard where you interface with it, and deeply connected where it interfaces with everything else.
Why "radically standard" matters
Your repository is the one asset you must never feel locked into. Rezee hosts plain git over smart HTTP and SSH - no custom client, no proprietary format; migration in (or out) is git remote add and git push, with full history, branches, and tags. We wrote about how that transport is built - a thin, boring pipe to the real git binary, which is exactly what you want between your code and the network.
The connection side is where the layer earns its place in a workspace: every PR knows its issue, every merge tells the tracker, and the spec that argued for the work reads its status live. Standard at the edge, connected at the core.
What's actually in the layer?
Repos and pull request review. Browse code and history, read the diff, comment on the change, and record a verdict - approved or changes requested - that stands until you replace it. The discussion is preserved with the PR, and you cannot review your own: the conditions good review practice needs.
Branch compare and protection. Three-dot compares, required approvals on protected branches, and merges gated on CI. The "required" part matters more every year - it's what makes the pipeline an honest referee for humans and agents alike.
YAML pipelines. One file in the repo defines the whole pipeline - triggers, jobs, steps, artifacts - in the shape we teach in the beginner's guide. No pipeline UI archaeology; the pipeline is code-reviewed like everything else.
Isolated steps, encrypted secrets. Every step runs in its own throwaway container; secrets are encrypted at rest with AES-256-GCM, decrypted only when a run is dispatched, and masked in logs.
Live log streaming. Logs stream as they happen, with a jump to the first failure. Watching a pipeline should feel like watching a terminal, not refreshing a page.
Auto-linked everything. The branch name links the chain: issue → branch → PR → merge → closed issue. The closed loop, seen from the code's side.
How does it connect to the other layers?
PRs and commits unfurl live in chat; merges update issues in Plan & Track, which the originating spec reads back through its references; pipelines report where the team already looks. And it's the layer where agent teammates do their most visible work - first-pass review, CI-failure diagnosis - inside the same gates humans pass through: required approvals, required checks, human merge.
FAQ
What is Rezee's Code & Ship layer?
The code layer of the Rezee workspace: git hosting over HTTPS and SSH, pull-request review, branch protection, and YAML-defined CI/CD pipelines running in isolated containers with encrypted secrets and live logs.
Can I migrate my existing repos to Rezee?
Yes - Rezee hosts standard git, so migration is adding a remote and pushing; history, branches, and tags come with. CI workflows from other platforms need translating into Rezee's pipeline YAML - typically the largest task, as we noted in Rezee vs GitHub.
How do CI minutes work?
Every plan includes a monthly pool of managed minutes (3,000 on Startup, 10,000 on Business) running in isolated cloud containers; additional minutes are billed per-minute. Details on pricing.