docs: clarify factory code forge setup - #752
rachaelrenk wants to merge 8 commits into
Conversation
Co-Authored-By: Warp <agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
![warp-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
There was a problem hiding this comment.
Overview
This PR adds a factory docs page for repositories on code forges without first-class factory support, updates related factory pages, and moves GitHub and GitLab into a new Code forges sidebar group. The docs content generally follows the repository style and the added links resolve, but the agent-doc review contract is incomplete.
Concerns
- 🚨 [CRITICAL] The diff adds VERIFY markers in
src/content/docs/factories/code-forges/other-code-forges.mdx:28andsrc/content/docs/factories/code-forges/other-code-forges.mdx:43, but the PR body does not include the required## Unverified claimssection listing them exactly. The contract checker treats this as a structural violation. ⚠️ [IMPORTANT] The PR description's Content design plan contains repeated, corrupted text; clean it up so reviewers can evaluate the rationale and unverified claims.- Security pass: no additional security findings in the diff; the docs avoid embedding token values and instruct using scoped repository tokens through secrets.
- Spec check: no approved or repository spec context was attached.
Verdict
Found: 1 critical, 1 important, 0 suggestions
Request changes
Comment /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
|
/warp-agent-review |
|
I'm re-reviewing this pull request in response to a review request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
There was a problem hiding this comment.
Overview
This PR adds a procedural page for connecting factories to repositories on code forges without first-class factory support, groups code-forge pages in the Factories sidebar, and updates related factory setup pages to point to the fallback path.
Concerns
- No blocking concerns found. The PR body identifies the unverified live UI and secret-injection claims, declares engineering-review-required risk, and the diff's internal links and navigation changes are consistent with the existing docs structure.
- No security findings. The new guidance keeps repository tokens in Agent Secrets and avoids placing token values directly in docs or configuration examples.
- No approved or repository spec context was provided, so there is no implementation-vs-spec drift to report.
Verdict
Found: 0 critical, 0 important, 0 suggestions
Approve
Comment /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
| Runner setup commands prepare each agent workspace before factory work starts. | ||
|
|
||
| 1. In the factory dashboard, open **Settings** > **Runners**. | ||
| 2. Open the default runner and add an authenticated `git clone` command that reads `$CODE_FORGE_TOKEN`. |
There was a problem hiding this comment.
The process is actually: click the edit button (pencil) next to the default runner, scroll to the "Setup commands" section, click + to add a new command.
Co-Authored-By: Warp <agent@warp.dev>
Co-Authored-By: Warp <agent@warp.dev>
This reverts commit 8f0bf7c.
1 participant
What this feature does
Factories can work with repositories on code forges without first-class support. The docs show factory administrators how to clone those repositories with an Agent Secret and default-runner setup commands, while making clear that provider-specific events and automations are unavailable. Available in Warp Factories Early Access since
v0.2026.08.26.17.59(2026-08-27).Summary
Clarifies the code-forge setup path for Warp Factories and separates repository access from work-source integrations.
Changes
Content design plan
Audience and JTBD: An engineering or factory administrator who needs their factory to work in a Git repository hosted outside GitHub or GitLab.com.
Problem: The factory setup wizard offers first-class GitHub and GitLab.com connections, but the supported no-provider path for another code forge is not documented. The administrator cannot infer that they must select No repo, configure the default runner’s setup commands, and grant the credential as an Agent Secret.
Goals:
Purpose and value: The existing Azure DevOps, Bitbucket, and self-managed GitLab pages apply to standalone cloud-agent environments, not factory setup. A focused factory procedure prevents readers from following the wrong flow.
Content type: Procedural — the reader is completing a setup task.
Skill and template:
draft_procedural/.agents/templates/procedural.mdHigh-impact scenarios:
Unverified claims
None — the reviewed UI labels and procedure steps are confirmed, and the source contains no
VERIFYmarkers.Documentation risk
Risk: engineering-review-required
Rationale: Adds a new factory setup procedure with reviewed UI labels and runtime behavior.
Docs override: none
Requested engineering reviewer: Safia (contacted in Slack; the
safiaGitHub account cannot be requested on this repository).Engineering review status: pending
Co-Authored-By: Warp agent@warp.dev