Pillion uses its own version control system to store and publish source. Git compatibility connects your existing clients to that source.
Agent tasks, Changes, and conversations describe different parts of the work. Keeping them separate lets you select source and context for review.
Understand the source model
- A Repository holds source history and controls access.
- A Change keeps one identity as its source develops across revisions and task attempts.
- A Source revision records a fixed file state and its parent revisions.
- An Agent task records requested work, source, attempts, and results.
- A Checkpoint retains selected source and task context for its stated retention period.
- An Integration candidate fixes the proposed result, selected revisions, target state, and workflow source for validation.
Open Changes in the repository to inspect saved revisions. Use Compare tasks to inspect recorded attempts.
Changes keep their identity when source revisions change. Checks and approvals still apply to the exact candidate they validate.
Publish the result you review
A candidate records the exact source for checks and approval. If the target changes, prepare a new candidate and validate it again.
Unresolved conflicts remain draft work. Resolve them before publishing a source revision.
Repository permissions, required reviews, and checks still apply. An agent task cannot approve or publish itself through its delegated task credential.
Private conversations remain separate from source. Share selected events when they help explain a pull request.
Keep your Git workflow
Use Git to clone, fetch, commit locally, and push. Pillion exposes compatible Git history for its published source.
git clone https://pillion.dev/OWNER/REPOSITORY.git
cd REPOSITORY
git switch -c improve-readmeReplace the example URL with your repository’s clone URL. Set up HTTPS or SSH authentication before accessing private source.
A push imports your proposed source into Pillion. Pillion checks permissions and the expected branch state before accepting the update.
Your local Git repository still uses Git commits and branches. Pillion assigns native source revisions their own identifiers.
A native revision has a stable Git compatibility mapping. Its Git object ID and native revision ID serve different interfaces.
Imported Git commits, tags, and signatures retain their original bytes. A signature covers its original Git object.
Choose the repository’s Git object format when creating it. That compatibility setting stays fixed and remains separate from native revision identity.
Read Everyday Git for the daily workflow, or bring an existing Git project.
Check compatibility at each boundary
Git compatibility covers source transport and history. GitHub API and workflow compatibility have separate documented limits.
- Pull requests provide source review, discussion, and merge requirements.
- Workflows use a supported subset of GitHub Actions syntax.
- The API provides GitHub-shaped resources and Pillion features.
- Git LFS transfers large-file payloads separately from source history.
Unsupported source representations or push options return errors. They do not silently change published refs.
Export source and private records separately
Git gives you a portable copy of the published source refs you can access. For a local mirror:
git clone --mirror https://pillion.dev/OWNER/REPOSITORY.git REPOSITORY.gitThe mirror contains Git history and advertised refs. It does not include private draft revisions, conversation records, issues, or pull request discussions.
LFS payloads require a separate LFS transfer. A Git mirror alone is not a complete repository backup.
Use Export thread for an authorized conversation export. Keep private collaboration records separate from source exports.
Published source retention remains independent of private conversation retention. Deleting a conversation does not remove the code that its pull request publishes.
Make your first agent change
Follow Your first agent change to connect a harness, save work, and share context for review.