Gitslice docs

For Git Users

Use this page if your mental model starts with repos, branches, commits, and pull requests. Gitslice keeps familiar boundaries but changes the native write path.

Git to Gitslice

Git term	Gitslice term
Git repository	Slice
Pull request	Changeset
Commit you make locally	Patchset/change content in a changeset
Merged commit on main	Native commit created when a changeset lands
main branch	Latest accepted tree at refs/global/main
Working tree	Workspace
Clone URL	Per-slice Git endpoint when Git HTTP is enabled

Familiar workflow, native submit

gs auth login
gs init <account>:<slice>
# edit files
gs status
gs create --message "change title"
gs submit

The important shift: you do not need to create a local commit before review. A changeset is the review unit, and submit creates the accepted native snapshot.

Do I still make commits?

In normal Gitslice work, no. You edit files, create a changeset, and submit it. The system creates the accepted native commit after submit validation passes.

What replaces a pull request?

A changeset. It is scoped to one authoring slice, carries patchsets, and is the unit that submit validation accepts or rejects.

Where is main?

The accepted tree is the native ref refs/global/main. The web UI usually calls it latest or main tree.

Can one change touch multiple repositories?

A changeset can only touch paths included by its authoring slice. If you need broader work, define a slice that includes the intended paths.

Can I clone with Git?

Yes when the deployment enables the Git smart-HTTP gateway. Use the Clone dropdown on a slice page for the concrete URL.