Repositories

Moving code in and out of a repository and setting the rules that govern it: Git access over SSH and HTTPS, the built-in issue tracker, keeping a repository in step with a remote, and gating what may land on a branch. Everything here is per-repository configuration; the instance-wide switches behind these features live in the admin documentation set.

Pages

• Git protocol — Cloning and pushing over SSH and HTTPS, including the accepted key types, an ~/.ssh/config block for a non-standard port, and the repo:write scope a token needs before a push is accepted.
• Issue tracker — The REST API for issues, comments, labels, and milestones, with full-text search and the closes #N keywords that close an issue when a merge request lands.
• Protected branch rules — Two independent protection surfaces: glob-matched rules gating merges on review counts and status checks, and the simple model that carries the require_pipeline CI gate.
• Repository mirroring — Pull and push mirrors created through the mirrors API, their stored credentials and status values, and the force-update a pull mirror applies over local changes to mirrored branches.