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 into the console or deleting repository, log in to the console with a SourceCommit customer account or a sub account that has "write" (WRITE) or higher permissions. For more information on how to assign the sub accounts permission, see Sub Account user guides.

Checking change history

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

Check commit history

To check the commit history, follow these steps:

  1. From the NAVER Cloud Platform console, navigate to i_menu > Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit screen and click the [Go to code] button.
    • You can also click the repository name on the repository list.
  3. Click the [Commit] tab on the repository's detail feature page.
  4. Check the created commit on the commit list and details.
    • Commit message: click to check the details of the commit.
    • Commit: click to check the commit file list.
      sourcecommit-use_manage1_ko

Check branch graph

If you create the branch, edit the file included in the repository, and merge, you can check the change history through the branch graphs.

Note

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

To view branch graphs, follow these steps:

  1. From the NAVER Cloud Platform console, navigate to i_menu > Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit screen and click the [Go to code] button.
    • You can also click the repository name on the repository list.
  3. Click the [Graph] tab on the repository's detail feature page.
  4. Check the history of changes and merging by the graphs and commit lists.
    • Graph/last date edited: check the date when the branches are created and merged.
    • Commit message: click to check the details of the commit.
    • Commit: click to check the commit file list.
      sourcecommit-use_manage2_ko

Branch management

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

Create branch

To create a branch, follow these steps:

  1. From the NAVER Cloud Platform console, navigate to i_menu > Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit screen and click the [Go to code] button.
    • You can also click the repository name on the repository list.
  3. Click branch/tag name items (default: master).
    • The branch/tag list window appears.
      sourcecommit-use_manage3_ko
  4. Click the [Branch] tab on the window and click the [Create] button.
  5. Enter the setting information in the branch creation popup window.
    • Branch name: enter the branch name you want 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 on the branch/tag name items.

Change current branch

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

Note

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

To change a branch, follow these steps:

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

Delete branch

If you add a branch to the repository except for the default branch (master), you can delete the branch you don't use.

Note

For more information on the branch creation, see Create branch.

Caution

Before you delete the branch, verify that the branch is no longer needed. You cannot restore the deleted branch.

To delete a branch, follow these steps:

  1. From the NAVER Cloud Platform console, navigate to i_menu > Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit screen and click the [Go to code] button.
    • You can also click the repository name on the repository list.
  3. Click the branch/tag name item.
    • The branch/tag list window appears.
  4. Click the [Branch] tab on the window and i-sourcecommit-more.png > [Delete] button on the right side of the branch you want to delete.
  5. Enter the branch name to be deleted into the popup window and click the [Delete] button.
    • Enter the branch name into the branch deletion popup window correctly to enable the [Delete] button.
Note
  • You cannot delete the default branch (master) and branch of an open pull request.
  • If you delete the selected branch, the default branch (master) is to be selected automatically.
  • After you delete the SourceCommit's repository branch, the repository replicated into the local PC may have a copy of the branch.

Tag management

You can check the repository changes by creating tags.

Note

To check changes, select tags. But you cannot edit or delete the file. Edit or delete the file after you select the branch if necessary. (For more information, see Change current branch.)

Create tag

To create a tag, follow these steps:

  1. From the NAVER Cloud Platform console, navigate to i_menu > Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit screen and click the [Go to code] button.
    • You can also click the repository name on the repository list.
  3. Click branch/tag name items (default: master).
    • The branch/tag list window appears.
      sourcecommit-use_manage6_ko
  4. Click the [Tag] tab on the window and click the [Create] button.
  5. Enter the setting information in the tag creation popup window.
    • Tag name: enter the tag name you want to create.
    • Create from the following: select the reference branch for a new tag.
  6. Click [Create].
    • The created tag name is displayed on the branch/tag name item.

Change current tag

If you add a tag to the repository, go to the tag to check changes.

To change a tag, follow these steps:

  1. From the NAVER Cloud Platform console, navigate to i_menu > Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit screen and click the [Go to code] button.
    • You can also click the repository name on the repository list.
  3. Click the branch/tag name item.
    • The branch/tag list window appears.
      sourcecommit-use_manage8_ko
  4. Click the [Tag] tab on the window and the tag name to use.
    • Enter the tag name into the search bar. Click i-sourcecommit-find to easily find the tag you want.
    • The selected tag name is displayed on the branch/tag name item.

Delete tag

If you add a tag to the repository, you can delete the tag you don't use.

Note

For more information on the tag creation, see Create tag.

Caution

Before you delete the tag, verify that the tag is no longer needed. You cannot restore the deleted tag.

To delete a tag, follow these steps:

  1. From the NAVER Cloud Platform console, navigate to i_menu > Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit screen and click the [Go to code] button.
    • You can also click the repository name on the repository list.
  3. Click the branch/tag name item.
    • The branch/tag list window appears.
  4. Click the [Tag] tab on the window and i-sourcecommit-more.png > [delete] button on the right side of the tag you want to delete.
  5. Enter the tag name to be deleted into the deletion popup window and click the [Delete] button.
    • Enter the tag name into the tag deletion popup window correctly to enable the [Delete] button.
Note
  • If you delete the selected tag, the default branch (master) is to be selected automatically.
  • After you delete the SourceCommit's repository tag, the repository replicated into the local PC may have a copy of the branch.

Using pull request

To apply changes to key branch such as the release branch, use pull request. You can review changes between each branch of the repository and merge the edited code file. You can also enhance the quality of each build in application development.
To create pull request, you need a source branch and a target branch.

  • Source branch: the branch where the changes were made.
  • Target branch: the branch where the changes will be included.
Note

For more information on the branch creation, see Create branch.

Create pull request

To create a pull request, follow these steps:

  1. From the NAVER Cloud Platform console, navigate to i_menu > Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit screen and click the [Go to code] button.
    • You can also click the repository name on the repository list.
  3. Click the [Pull Request] tab on the repository's detail feature page.
    • If there are existing pull requests, a list of pull requests is displayed.
    • You can display the pull request you want to the list by setting Status filter in the top right.
  4. Click the [Create pull request] button, set the Compare branch item on the window, and click the [Select] button.
    • Target: select the target branch to include changes.
    • Source: select the source branch that applied changes.
      sourcecommit-use_pr2_ko
  5. Enter the title and description into Title and Description.
    • If you must change the selected Target branch or Source branch, change settings and click the [Reselect] button.
    • To verify detailed change history, click the [Commits] and [Files changed] tabs.
      • [Commits] tab: check the commit change history, head (HEAD), or the entire commit list by clicking Commit message or Commit on the list.
      • [Files changed] tab: check the detailed changes for each file on the file comparison window.
        sourcecommit-use_pr3_ko
  6. Click [Create].
    • The list displays open status of new pull request.

Pull request process

To process an open pull request, follow these steps:

  1. From the NAVER Cloud Platform console, navigate to i_menu > Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit screen and click the [Go to code] button.
    • You can also click the repository name on the repository list.
  3. Click the [Pull Request] tab on the repository's detail feature page.
    • You can check the open pull request on the list.
    • You can only display the open pull request to the list by setting Status filter to Open in the top right.
  4. To precess, click pull request items on the list.
  5. Check the detailed change history in the Pull request content.
    • You can edit the name and description by clicking the [Edit] button on the right side of Pull request content.
    • To check the detailed change history, click the [Comments], [Commits], and [Files changed] tabs.
      • [Comments] tab: check the comments or add a new comment by clicking the [Add] button.
      • [Commits] tab: check the commit change history, head (HEAD), or the entire commit list by clicking Commit message or Commit on the list.
      • [Files changed] tab: check the detailed changes for each file on the file comparison window.
        sourcecommit-use_pr4_ko
  6. To process the pull request, click next on the right side of Pull request content.
    • [Merge]: merge changes of the source branch through a new commit. Click the [Apply] button after you check and edit the following settings on the merge popup window:
      sourcecommit-use_pr5_ko
      • Merge strategy: displays the strategy of merging changes.
      • Creator name, email address: change the auto-entered name and email, if necessary.
      • Commit message: change the auto-entered default message, if necessary.
    • [Close pull request]: close the pull request. Click the [Close] button on the close pull request popup window.
      sourcecommit-use_pr6_ko
Note

Your log-in account is automatically entered into Name and Email address in the merge popup window.

  • Name becomes user.name of the new commit.
  • Email address becomes user.email of the new commit.

Pull request conflict solution

If you edit the same file in the default branch (master) and the new branch simultaneously, the conflict message is displayed in the process of pull request creation.

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

To merge the branch, resolve the conflict using Git client from the repository replicated into a local PC.

If the target branch is "master," the source branch is "issue," and the conflict file is "file.txt.," to solve the conflict between branches using Git client, follow these steps:

  1. Checkout to the target branch from the repository replicated into a local PC.
$ git checkout master
  1. 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.
  1. Check the list of files the conflict 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
  1. Open the file the conflict occurred and check content.
    • The conflict content between both branches is displayed as follows:
 <<<<<<< HEAD
 master: the content of target branch
 =======
 issue: the content of source branch
 >>>>>>> issue
  1. Edit the overlapped conflict and save the file.

    • Completely delete the marker (<<<<<< HEAD ~ >>>>>> issue) automatically entered before you save the file.
  2. Upload (push) the edited file to the remote storage (SourceCommit repository).

$ git add file.txt

$ git commit

$ git push

Changing repository settings

You can change the default branch of repository, the description you entered to create the repository, and NAVER Cloud Platform's File Safer integrations setting.

Change default branch

To change the default branch of the repository, follow these steps:

  1. From the NAVER Cloud Platform console, navigate to i_menu > Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit page and click the [Change settings] button.
  3. Click the list of Default branch on the repository settings page. Select the branch and click the [Save] button.
Note

When you open the repository replicated into a local PC using Git client, the default branch settings may not be correctly applied. Update the Git client to the latest version (v1.8.4.3 or above recommended).

Change repository description

To change the repository description, follow these steps:

  1. From the NAVER Cloud Platform console, navigate to i_menu > Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit page and click the [Change settings] button.
  3. Edit the Repository description on the settings page and click the [Save] button.

File Safer integrations settings

To edit NAVER Cloud Platform's File Safer integrations, follow these steps:

Note

If you clear File Safer integrations, the usage status of File Safer does not change. To unsubscribe File Safer, click Services > Security > File Safer > Subscription.

  1. From the NAVER Cloud Platform console, navigate to i_menu > Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit page and click the [Change settings] button.
  3. In the Security product integrations of the settings page, click the box of FILE SAFER (FILE FILTER) integrations to select or deselect and click the [Save] button.

Object Storage integrations activation settings

To change NAVER Cloud Platform's Object Storage integrations settings, follow these steps:

Note

Even if you clear Object Storage (bucket) integration of the repository, the integrations settings of SourceCommit's Object Storage does not change. The existing data in the bucket remains.

  1. From the NAVER Cloud Platform console, navigate to i_menu > Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit page and click the [Change settings] button.
  3. In the Object Storage service integration of the settings page, click the box of Integrate Git LFS with Object Storage bucket to select or deselect and click the [Save] button.

Deleting repository

You can delete a repository you are no longer using.

Caution

Before you delete the repository, verify that the repository is no longer needed. You cannot restore the deleted repository.

To delete a repository, follow these steps:

  1. From the NAVER Cloud Platform console, navigate to i_menu > Services > Developer Tools > SourceCommit.
  2. Select a repository on the SourceCommit page and click the [Delete] button.
  3. Enter the repository name into the deletion popup window and click the [Delete] button.
Note
  • Enter the repository name into the repository deletion popup window correctly to enable the [Delete] button.
  • After you delete the SourceCommit repository, a copy of repository may remain on a local PC.