Sapient Forge (code)
Sapient Forge is Sapient’s own git host. If you’d rather not connect a GitHub account — or you want a product up before you’ve decided where its code should live — your factory can put the repository here instead. There’s no account to create and nothing to install.
What it enables: your engineering seats clone, branch, open pull requests, review, and merge exactly as they would on GitHub. Nothing else in the factory changes.
What your engineers get
Section titled “What your engineers get”The same workflow, on the same conventions:
| A repository per product | Created and registered to your factory when the product’s repository is set up. Your seats clone and push over HTTPS. |
| Pull requests | One per story, with the diff, the review conversation, and the merge. |
| A required review check | A pull request cannot merge until the code review passes. This is enforced by the host, not by policy — a merge attempt on an unreviewed branch is refused. |
| Squash merges | One commit per story on the main branch. |
| Browsable code | The control room reads directly from Forge — files, trees, branches, history, and the diff on any pull request. |
Forge implements the GitHub API surface Sapient itself uses, so everything downstream — the review gate, the deploy trigger, the code viewer — behaves identically whichever one you’re on. It is not a general-purpose GitHub replacement: it serves the workflow your factory runs, not the whole GitHub feature set.
Looking at your code
Section titled “Looking at your code”Settings → Connectors → Sapient Works hosted apps → Browse repositories opens the Forge viewer. Pick a repository and you get two tabs:
- Source — the file tree and the file, read live from the repository’s default branch. It opens on the README when there is one.
- Branches & merges — every branch with its head commit, and the recent history of the default branch. The branch your factory protects is labelled: that is the one where a merge is refused until the code review passes.
Because Forge squash-merges, a story that lands shows up as one commit on the main branch rather than a merge of its branch — the story’s changes are there, its individual work-in-progress commits are not. That’s the same history your engineering seats see.
Reading your code here doesn’t cost credits. The engineering work that produced it already did.
Choosing between Forge and GitHub
Section titled “Choosing between Forge and GitHub”| Sapient Forge | GitHub | |
|---|---|---|
| Setup | none | install the Sapient app on your org |
| Where the code lives | Sapient’s infrastructure | your GitHub organization |
| Your team can clone it | not today | yes, it’s your repo |
| Your own CI | no | yes |
| Best for | getting a product moving before you’ve picked a home for it; demos | anything you intend to keep |
Forge is not a long-term home for code you care about. It’s scoped to Sapient-hosted products, it holds no third-party integrations, and your own engineers can’t clone from it today. If you know the product matters, connect GitHub up front and skip the move later.
Connecting it
Section titled “Connecting it”Sapient Forge is enabled for your factory by Sapient, not by pasting a credential. It appears under Settings → Connectors in the Sapient Works hosted apps group. The same connector enables Sapient Deploy, Sapient Base and Sapient Pulse, so all four cards turn on together — but the resources themselves are still created per product: a repository when the product’s code is set up, a database when you approve its provisioning request, a site when it first deploys.