Deckhouse Code is where a team keeps its source code, reviews changes, and runs CI/CD pipelines. The Usage section covers the everyday work of a project member or a group owner, from the first sign-in to searching across the instance.
Sign in to the web interface with your account credentials or through an external identity provider, then clone a repository and push changes over SSH or HTTPS. See Signing in.
A group brings projects together under a shared role model and shared policies such as protected branches and push rules; a project holds a repository, its issues, and its wiki. See Groups and members.
A repository stores the Git history of a project: branches, tags, and files edited through the web interface or Git LFS. Protected branches, push rules, and pull mirroring control how changes reach it. See Managing Git repositories.
A merge request combines changes from one branch into another through review: comments, approval rules, and external status checks decide when it can merge. See Code review.
A pipeline defined in .gitlab-ci.yml builds, tests, and deploys a project’s code, with secrets available from an external Vault or Deckhouse Stronghold. See CI/CD pipelines.
Group owners and project maintainers apply security settings such as visibility levels, push rule enforcement, and merge checks to protect the codebase. See Group and project security settings.
Webhooks notify external systems about events in a group, project, or subgroup. See Webhooks.
Advanced search finds code, commits, issues, and merge requests across the projects you have access to. See Advanced search.