Documentation Index

Fetch the complete documentation index at: https://guide.ncloud-docs.com/llms.txt

Use this file to discover all available pages before exploring further.

Repository management

Prev Next

Available in Classic and VPC

After selecting a repository, you can check the commit history or create or delete branches and tags. You can also merge branch-level changes by creating and checking pull requests, as well as change repository settings or delete the repository.

Note

To perform SourceCommit management, such as merging changes or deleting a repository, log in to the console with a SourceCommit account or a sub account that has "write" (WRITE) or higher permissions. For more information on how to assign permissions to sub accounts, see Sub Account user guide.

Check change history

You can check the change history of the selected repository using the commit list and branch graphs.

Check commit history

To check the commit history:

  1. In the NAVER Cloud Platform console, navigate to Menu > All Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit interface, then click [Go to code].
    • You can also click the repository name in the repository list.
  3. Click the [Commit] tab on the repository detail interface.
  4. Check the created commits in the commit list and view their details.
    • Commit message: Click to check the details of the commit.
    • Commit: Click to check the file list of the commit.
      sourcecommit-use_manage1_ko

Check branch graph

If you created a branch, edited files in the repository, and merged them, you can check the change history through the branch graph.

Note

For more information on branch creation and merging changes, see Create branch and Using pull requests.

To check the branch graph:

  1. In the NAVER Cloud Platform console, navigate to Menu > All Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit interface, then click [Go to code].
    • You can also click the repository name in the repository list.
  3. Click the [Graph] tab on the repository detail interface.
  4. Check the change and merge history using the graph and commit list.
    • Graph/Last modified date: Check the timing of branch creation and merging.
    • Commit message: Click to check the details of the commit.
    • Commit: Click to check the file list of the commit.
      sourcecommit-use_manage2_ko

Manage branches

You can create a branch in the repository, make changes, and merge or delete the created branch.

Create branch

To create a branch:

  1. In the NAVER Cloud Platform console, navigate to Menu > All Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit interface, then click [Go to code].
    • You can also click the repository name in the repository list.
  3. Click the branch/tag name field (default: master).
    • The branch/tag list window appears.
      sourcecommit-use_manage3_ko
  4. Click the [Branch] tab in the branch/tag list window, and click [Create].
  5. Enter the setting information in the branch creation popup window.
    • Branch name: Enter the branch name to create.
    • Create from the following: Select the reference branch or tag for a new branch.
  6. Click [Create].
    • You can check the newly created branch name in the branch/tag name field.

Change current branch

If you add branches to the repository other than the default branch (master), you can change the branch, edit repository content, and merge with the desired branch.

Note

For more information on branch creation and merging changes, see Create branch and Using pull requests.

To change a branch:

  1. In the NAVER Cloud Platform console, navigate to Menu > All Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit interface, then click [Go to code].
    • You can also click the repository name in the repository list.
  3. Click the branch/tag name field (default: master).
    • The branch/tag list window appears.
      sourcecommit-use_manage5_ko
  4. Click the [Branch] tab in the branch/tag list window, and click the branch name to use.
    • Enter the branch name into the search bar, and click i-sourcecommit-find to easily find the desired branch.
    • You can check the newly selected branch name in the branch/tag name field.

Delete branch

If you add branches to the repository other than the default branch (master), you can delete branches you no longer use.

Note

For more information on branch creation, see Create branch.

Caution

Before deleting the branch, verify that it is no longer needed. Deleted branches cannot be restored.

To delete a branch:

  1. In the NAVER Cloud Platform console, navigate to Menu > All Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit interface, then click [Go to code].
    • You can also click the repository name in the repository list.
  3. Click the branch/tag name field.
    • The branch/tag list window appears.
  4. Click the [Branch] tab in the branch/tag list window, and then click i-sourcecommit-more.png > [Delete] on the right side of the branch to delete.
  5. Enter the name of the branch to delete in the branch deletion popup window, and click [Delete].
    • The [Delete] button is not enabled until you enter the branch name correctly in the branch deletion popup window.
Note
  • You cannot delete the default branch (master) or a branch with an open pull request from the console.
  • If you delete the selected branch, the default branch (master) is automatically selected.
  • Even after you delete a branch in a SourceCommit repository, a copy of the branch may remain in the repository replicated to your local PC.

Manage tags

You can use the created tags to check changes in the repository.

Note

Selecting a tag allows you to check changes at that point in time, but you cannot edit or delete files. If necessary, select a branch and then edit or delete files (see Change current branch).

Create tag

To create a tag:

  1. In the NAVER Cloud Platform console, navigate to Menu > All Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit interface, then click [Go to code].
    • You can also click the repository name in the repository list.
  3. Click the branch/tag name field (default: master).
    • The branch/tag list window appears.
      sourcecommit-use_manage6_ko
  4. Click the [Tag] tab in the branch/tag list window, and click [Create].
  5. Enter the setting information in the tag creation popup window.
    • Tag name: Enter the tag name to create.
    • Create from the following: Select the reference branch for a new tag.
  6. Click [Create].
    • You can check the newly created tag name in the branch/tag name field.

Change current tag

If you add a tag to the repository, you can move to that tag to check changes.

To change a tag:

  1. In the NAVER Cloud Platform console, navigate to Menu > All Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit interface, then click [Go to code].
    • You can also click the repository name in the repository list.
  3. Click the branch/tag name field.
    • The branch/tag list window appears.
      sourcecommit-use_manage8_ko
  4. Click the [Tag] tab in the branch/tag list window, and click the tag name to use.
    • Enter the tag name into the search bar, and click i-sourcecommit-find to easily find the desired tag.
    • You can check the newly selected tag name in the branch/tag name field.

Delete tag

If you add a tag to the repository, you can delete tags you no longer use.

Note

For more information on tag creation, see Create tag.

Caution

Before deleting the tag, verify that it is no longer needed. Deleted tags cannot be restored.

To delete a tag:

  1. In the NAVER Cloud Platform console, navigate to Menu > All Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit interface, then click [Go to code].
    • You can also click the repository name in the repository list.
  3. Click the branch/tag name field.
    • The branch/tag list window appears.
  4. Click the [Tag] tab in the branch/tag list window, and then click i-sourcecommit-more.png > [Delete] on the right side of the tag to delete.
  5. Enter the name of the tag to delete in the tag deletion popup window, and click [Delete].
    • The [Delete] button is not enabled until you enter the tag name correctly in the tag deletion popup window.
Note
  • If you delete the selected tag, the default branch (master) is automatically selected.
  • Even after you delete a tag in a SourceCommit repository, a copy of the tag may remain in the repository cloned to your local PC.

Use pull requests

Using pull requests when applying changes to key branches, such as the release branch, allows multiple users to review changes between repository branches and merge edited code files, ensuring the quality of each build during application development.
To create a pull request, you need a source branch and a target branch.

  • Source branch: Branch with updated changes
  • Target branch: Branch containing changes
Note

For more information on branch creation, see Create branch.

Create pull requests

To create a pull request:

  1. In the NAVER Cloud Platform console, navigate to Menu > All Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit interface, then click [Go to code].
    • You can also click the repository name in the repository list.
  3. Click the [Pull Request] tab on the repository detail interface.
    • If there are existing pull requests, a list of pull requests is displayed.
    • You can filter the list to display only pull requests in the desired status by setting the Status filter at the top right of the list.
  4. Click [Create pull request], set the Compare branch item on the interface, and click [Select].
    • Target: Select the target branch to include changes.
    • Source: Select the source branch with updated changes.
      sourcecommit-use_pr2_ko
  5. Enter a title and description of pull request in Title and Description.
    • If you need to change the selected Target or Source branch, change the settings and click [Reselect].
    • You can check the detailed change history of the branch by clicking the [Commits] and [Files changed] tabs.
      • [Commits] tab: Click Commit message or Commit in the commit list to check the change history, head (HEAD), or entire list of the commit.
      • [Files changed] tab: Check detailed changes for each file in the file comparison window.
        sourcecommit-use_pr3_ko
  6. Click [Create].
    • The newly created pull request is displayed with Open status in the pull request list.

Process pull requests

To process an open pull request after creation:

  1. In the NAVER Cloud Platform console, navigate to Menu > All Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit interface, then click [Go to code].
    • You can also click the repository name in the repository list.
  3. Click the [Pull Request] tab on the repository detail interface.
    • You can check open pull requests in the list.
    • You can filter the list to display only open pull requests by setting the Status filter to Open at the top right of the list.
  4. Click the pull request item to process in the pull request list.
  5. Check the detailed change history in the Pull request content component.
    • You can edit the pull request name and description by clicking [Edit] on the right side of Pull request content.
    • You can check the detailed change history of the branch by clicking the [Comments], [Commits], and [Files changed] tabs.
      • [Comments] tab: Check the written comments or click [Add] to add a new comment.
      • [Commits] tab: Click Commit message or Commit in the commit list to check the change history, head (HEAD), or entire list of the commit.
      • [Files changed] tab: Check detailed changes for each file in the file comparison window.
        sourcecommit-use_pr4_ko
  6. To process the pull request, click one of the following buttons on the right side of the Pull request content component.
    • [Merge]: Merges changes of the source branch into the target branch through a new commit. Check and edit the following settings in the Merge popup window, and then click [Apply]:
      sourcecommit-use_pr5_ko
      • Merge strategy: Displays the merge strategy for changes.
      • Author name, Email address: Check the auto-entered author name and email address, and change them if necessary.
      • Commit message: Check the auto-entered default message, and change it if necessary.
    • [Close pull request]: Closes the pull request. Click [Close] in the Close pull request popup window.
      sourcecommit-use_pr6_ko
Note

In the Merge popup window, the account credentials of your logged-in account are automatically entered into Author name and Email address.

  • Author name becomes the user.name value of the created commit.
  • Email address becomes the user.email value of the created commit.

Resolve pull request conflicts

If you edit the same file in both the default branch (master) and a newly created branch, a conflict message is displayed when creating a pull request.

Note
  • Even if a conflict message appears, you can create a pull request.
  • When you open a pull request with conflicts in the pull request list, a message appears indicating that changes cannot be merged due to conflicts, and the [Merge] button is disabled, preventing you from merging.
    sourcecommit-use_pr7_ko

If a pull request conflict occurs, you can resolve the conflict using a Git client in the repository replicated to your local PC, and then merge the branch.

If the target branch is "master," the source branch is "issue," and the conflicting file is "file.txt," to resolve conflicts between branches using a Git client:

  1. Check out the target branch in the repository replicated to your local PC.
    $ git checkout master
    
  2. Merge the source branch.
    • If a conflict between branches is detected, the following message is displayed:
      $ git merge issue
      Auto-merging file.txt
       CONFLICT (add/add): Merge conflict in file.txt
       Automatic merge failed; fix conflicts and then commit the result.
      
  3. Check the list of files where conflicts occurred.
    $ git status
     On branch master
     Your branch is up-to-date with 'origin/master'.
     You have unmerged paths.
    (fix conflicts and run "git commit")
    
     Unmerged paths:
    (use "git add <file>..." to mark resolution)
    
         both added:      file.txt
    
  4. Open the conflicting file and check the conflict display section.
    • The conflict content between both branches is displayed as follows:
       <<<<<<< HEAD
       master: Content of the target branch
       =======
       issue: Content of the source branch
       >>>>>>> issue
      
  5. Resolve the conflicting content and save the file.
    • Before saving the file, completely delete the automatically inserted markers (<<<<<< HEAD - >>>>>> issue).
  6. Push the edited file to the remote repository (SourceCommit repository).
    $ git add file.txt
    
    $ git commit
    
    $ git push
    

Change repository settings

If necessary, you can change the default branch of the repository, the description entered when creating the repository, and the File Safer security product integration settings.

Change default branch

To change the default branch of the repository:

  1. In the NAVER Cloud Platform console, navigate to Menu > All Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit interface, then click [Change settings].
  3. On the repository settings interface, click the Default branch list, select a branch, and then click [Save].
Note

If the default branch setting is not correctly applied when opening a repository replicated to your local PC using a Git client, update the Git client to a higher version (v1.8.4.3 or higher recommended).

Change repository description

To change the repository description:

  1. In the NAVER Cloud Platform console, navigate to Menu > All Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit interface, then click [Change settings].
  3. On the repository settings interface, edit the description in Repository description, and then click [Save].

File Safer integration settings

To change the File Safer integration settings of the repository:

Note

Even if you disconnect File Safer integration for a repository, the subscription status of the File Safer service does not change. To unsubscribe from File Safer, unsubscribe from the service in Menu > All Services > Security > File Safer > Subscription.

  1. In the NAVER Cloud Platform console, navigate to Menu > All Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit interface, then click [Change settings].
  3. In the Security product integration component on the repository settings interface, click the checkbox for ** Integrate with FILE SAFER (FILE FILTER)** to select or clear it, and then click [Save].

Object Storage integration activation settings

To change the Object Storage integration activation settings of a repository:

Note

Even if you disable Object Storage (bucket) integration for a repository, the Object Storage integration status of the SourceCommit service does not change, and existing data in the bucket is not deleted.

  1. In the NAVER Cloud Platform console, navigate to Menu > All Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit interface, then click [Change settings].
  3. In the Object Storage service integration component on the repository settings interface, click the checkbox for Integrate Git LFS with Object Storage bucket to select or clear it, and then click [Save].

Delete repository

You can delete repositories you are no longer using.

Caution

Before deleting the repository, verify that it is no longer needed. Deleted repositories cannot be restored.

To delete a repository:

  1. In the NAVER Cloud Platform console, navigate to Menu > All Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit interface, then click [Delete].
  3. Enter the name of the repository to delete in the repository deletion popup window, and click [Delete].
Note
  • The [Delete] button is not enabled until you enter the repository name correctly in the repository deletion popup window.
  • Even after you delete a SourceCommit repository, a copy of the repository may remain on your local PC.