SourceCommit glossary

Available in Classic and VPC

There are a few terms you need to know to use SourceCommit. The terms and their descriptions are as follows.

Classic environment

A platform that does not provide Virtual Private Cloud (VPC), a customer-only private network, on public cloud

User Created

Policies arbitrarily created by account users on Sub Account of NAVER Cloud Platform

VPC environment

A platform that provides Virtual Private Cloud (VPC), a customer-only private network, on public cloud

Git

A distributed version-control system for managing the source code of programs

Repository

A storage that allows information scattered within an organization or information related to the development of an application system to be collected and shared

Branch

The independent version of the data that each user generated from a project. After modifying, changing, or adding files in a branch, the branch is merged into the master branch (main directory of a project) through a pull request to perform data updates

Sub Account

A sub account created under the default account (main account) that can be specified to manage permissions for each task and role

SourceDeploy

An automated deployment service that deploys and applies newly written or updated sources to the server automatically

SourceBuild

A managed source code building service that supports source code compiling, which includes code compile and test features, and component packaging all at once

SourceCommit

A private Git repository for secure storage and management of source code and files required for development

SourcePipeline

An automated service that supports fast and stable software releases by integrating repository, build, and deployment processes

Commit

A checkpoint that can be evaluated and recovered through snapshots. Created when modifying, changing, and adding a file

Tag

An easy-to-know name set to find the commit easily when using the Git repository to check the change history

Pull request

Review and merge requests created by each user after completing modification, change, and addition tasks of files in branch. Project managers open pull requests to review the source branch's changes, and then determine whether to apply (merge) the target branch.