Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions FAQ.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,21 @@ only one repository. Multiple repositories amplify the need for shared
inventory and workspace coordination, but they are not required for Base's
project contract to be useful.

### Can I use Base without GitHub?

Yes, for Base's local Git project loop. Base assumes Git as the source-control
system; Mercurial, Perforce, Subversion, Fossil, and other non-Git SCMs are out
of scope. A GitLab, Bitbucket, internal Git, or local Git repository can use
local Base commands once it is checked out locally and declares
`base_manifest.yaml`.

Base is still GitHub-primary for forge automation. Repository creation,
repository materialization, repository configuration, `basectl gh ...`,
GitHub Issues, pull requests, Projects, Actions intake, and release publishing
target GitHub today. See
[Source Control And Forge Support](docs/source-control-and-forge-support.md)
for command-by-command behavior.

## First-Time Installation

### What should I run on a blank macOS or Ubuntu/Debian machine?
Expand Down
7 changes: 4 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,8 +6,8 @@
![Version](https://img.shields.io/badge/version-1.8.0-blue)
[![License: Apache-2.0](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)

> Base is an AI-ready GitHub workspace control plane for repository setup, local
> development, and verified pull requests.
> Base is an AI-ready Git-based, GitHub-primary workspace control plane for
> repository setup, local development, and verified pull requests.

Base is the local operating contract you add to a repository set so its readiness,
trusted execution, onboarding, and handoff stop depending on private maintainer
Expand All @@ -25,7 +25,8 @@ Use Base when you need to:
handoff-ready pull request.

Base owns workspace orchestration, policy, trust, readiness, and handoff. Your
repositories own their source code, tests, and project behavior; GitHub owns
repositories own their source code, tests, and project behavior; Git remains the
SCM boundary; GitHub remains Base's first-class forge automation target for
hosting and pull requests; environment managers and AI tools remain adapters.
That boundary lets Base coordinate the workflow without turning your projects
into a monorepo or moving project-specific logic into Base.
Expand Down
Loading