- Print
- PDF
Managing repository
- Print
- PDF
Available in Classic and VPC
You can select a repository to check the commit history, or create or delete a branch or tag. You can also merge changes in the unit of a branch through creating and checking pull requests, change the repository settings, or delete the repository.
Log in to console using the SourceCommit customer account or the sub account with WRITE
permissions or greater for SourceCommit management such as integrating changes or deleting repositories. Refer to Sub Account Guide for how to set permissions for a sub account.
Check change history
You can check the selected repository's change history through a commit list and branch graph.
Check commit history
The following describes how to check the commit history.
Connect to the NAVER Cloud Platform console.
Click the Services > Developer Tools > SourceCommit menus, in that order.
Select a repository from the SourceCommit page, and then click the [Go to code] button.
- You can also click the repository name from the repository list.
From the Repository's detailed feature page, click the [Commit] tab.
Check the commit created from the commit list and its details.
- Commit message: Click to check the commit's details.
- Commit: Click to check the commit's file list.
Check branch graph
You can check the change history through a branch graph if you modified and merged a file included in a repository by creating a branch.
Refer to Create branch and Using pull request for details about creating a branch and merging changes.
The following describes how to check a branch graph.
Connect to the NAVER Cloud Platform console.
Click the Services > Developer Tools > SourceCommit menus, in that order.
Select a repository from the SourceCommit page, and then click the [Go to code] button.
- You can also click the repository name from the repository list.
From the Repository's detailed feature page, click the [Graph] tab.
Check the change and merging history through the graph and commit list.
- Graph/Last modified date: Checks the time of creating and merging the branch.
- Commit message: Click to check the commit's details.
- Commit: Click to check the commit's file list.
Manage branch
After creating a repository's branch and changing its content, you can delete a merged or created branch.
Create branch
The following describes how to create a branch.
Connect to the NAVER Cloud Platform console.
Click the Services > Developer Tools > SourceCommit menus, in that order.
Select a repository from the SourceCommit page, and then click the [Go to code] button.
- You can also click the repository name from the repository list.
Click the Branch/tag name item (default: master).
- The Branch/tag list window is shown.
Click the [Branch] tab in the Branch/tag list window, and then click the [Create] button.
Enter the settings information in the Create branch pop-up window.
- Branch name: Enter the name of the branch to be created.
- Create from: Select the standard branch or tag to be used when creating a new branch.
Click the [Create] button.
- You can check that a newly created branch name is shown in the Branch/tag name item.
Change current branch
If you add a branch other than the default branch (master) to a repository, then you can change the branch, modify the repository content, and merge it with the desired branch.
Refer to Create branch and Using pull request for details about creating a branch and merging changes.
The following describes how to change a branch.
Connect to the NAVER Cloud Platform console.
Click the Services > Developer Tools > SourceCommit menus, in that order.
Select a repository from the SourceCommit page, and then click the [Go to code] button.
- You can also click the repository name from the repository list.
Click the Branch/tag name item (default: master).
- The Branch/tag list window is shown.
Click the [Branch] tab in the Branch/tag list window, and then click the branch name to be used.
- You can enter the branch name in the search window and click to find the desired branch easily.
- You can check that a newly selected branch name is shown in the Branch/tag name item.
Delete branch
If you add a branch other than the default branch (master) to a repository, you can delete a branch that isn't used anymore.
Refer to Create branch for details about creating a branch.
Check once again if the branch is not needed anymore before deleting it. The deleted branch can't be recovered.
The following describes how to delete a branch.
- Connect to the NAVER Cloud Platform console.
- Click the Services > Developer Tools > SourceCommit menus, in that order.
- Select a repository from the SourceCommit page, and then click the [Go to code] button.
- You can also click the repository name from the repository list.
- Click the Branch/tag name item.
- The Branch/tag list window is shown.
- Click the [Branch] tab in the Branch/tag list window, and then click the > [Delete] buttons on the right of the branch to be deleted in order.
- Enter the branch name you want to delete in the Delete branch pop-up window, and then click the [Delete] button.
- The [Delete] button isn't enabled before entering the branch name correctly in the Delete branch pop-up window.
- A branch with an open default branch (master) and pull request can't be deleted in the console.
- If you delete a branch currently selected, the default branch (master) is automatically selected.
- The copy of the branch can remain in the repository copied to the local PC even after the SourceCommit repository's branch is deleted.
Manage tag
You can utilize this when you check the repository's changes by creating a tag.
Once you select a tag, you can check the changes at that time, but you can't modify or delete a file. Select a branch, and then modify or delete the file if required. (Refer to Change current branch)
Create tag
The following describes how to create a tag.
Connect to the NAVER Cloud Platform console.
Click the Services > Developer Tools > SourceCommit menus, in that order.
Select a repository from the SourceCommit page, and then click the [Go to code] button.
- You can also click the repository name from the repository list.
Click the Branch/tag name item (default: master).
- The Branch/tag list window is shown.
Click the [Tag] tab in the Branch/tag list window, and then click the [Create] button.
Enter the settings information in the Create tag pop-up window.
- Tag name: Enter the name of the tag to be created.
- Create from: Select the standard branch to be used when creating a new tag.
Click the [Create] button.
- You can check that a newly created tag name is shown in the Branch/tag name item.
Change current tag
If you add a tag to a repository, you can go to the tag to check the changes.
The following describes how to change a tag.
Connect to the NAVER Cloud Platform console.
Click the Services > Developer Tools > SourceCommit menus, in that order.
Select a repository from the SourceCommit page, and then click the [Go to code] button.
- You can also click the repository name from the repository list.
Click the Branch/tag name item.
- The Branch/tag list window is shown.
- The Branch/tag list window is shown.
Click the [Tag] tab in the Branch/tag list window, and then click the tag name to be used.
- You can enter the tag name in the search window and click to find the desired tag easily.
- You can check that a newly selected tag name is shown in the Branch/tag name item.
Delete tag
If you add a tag to a repository, you can delete a tag that is no longer used.
Refer to Create tag for details about creating a tag.
Check once again if the tag is not needed anymore before deleting it. The deleted tag can't be recovered.
The following describes how to delete a tag.
- Connect to the NAVER Cloud Platform console.
- Click the Services > Developer Tools > SourceCommit menus, in that order.
- Select a repository from the SourceCommit page, and then click the [Go to code] button.
- You can also click the repository name from the repository list.
- Click the Branch/tag name item.
- The Branch/tag list window is shown.
- Click the [Tag] tab in the Branch/tag list window, and then click the > [Delete] buttons on the right of the tag to be deleted in order.
- Enter the tag name in the Delete tag pop-up window, and then click the [Delete] button.
- The [Delete] button isn't enabled before entering the tag name correctly in the Delete tag pop-up window.
- If you delete a tag currently selected, the default branch (master) is automatically selected.
- The copy of the tag can remain in the repository copied to the local PC even after the SourceCommit repository's tag is deleted.
Using pull request
If you want to apply changes to an important branch like release branch, then you can utilize pull requests for multiple users to review the changes between each branch and merge the modified code file. In this way, you can secure each build's quality when developing an application.
The source branch and target branch are required to create a pull request.
- Source branch: the branch that has the changes reflected
- Target branch: the branch that the changes will be included
Refer to Create branch for details about creating a branch.
Create pull request
The following describes how to create a pull request.
Connect to the NAVER Cloud Platform console.
Click the Services > Developer Tools > SourceCommit menus, in that order.
Select a repository from the SourceCommit page, and then click the [Go to code] button.
- You can also click the repository name from the repository list.
From the Repository's detailed feature page, click the [Pull request] tab.
- If there is a pull request performed previously, a pull request list is shown.
- You can also set the Status filter on the upper right of the list to show pull requests of the desired status only in the list.
Click the [Create pull request] button, set the Compare branch item in the Create pull request page, and then click the [Select] button.
- Target: Select the target branch to include the changes.
- Source: Select the source branch that has the changes reflected.
Enter the pull request's title and description in Title and Description items, respectively.
- If you have to change the selected target branch or source branch, change the settings, and then click the [Select again] button.
- You can click the [Commits] and [Files changed] tabs to check the detailed change history of the branch.
- [Commits] tab: Click Commit message or Commit item in the commit list to check the commit's change history, HEAD, or the entire commit list.
- [Files changed] tab: Checks each file's detailed modification history in the Compare file window.
Click the [Create] button.
- A newly created pull request list is shown with the Opened status in the pull request list.
Process pull request
The following describes how to process a pull request opened after creating.
Connect to the NAVER Cloud Platform console.
Click the Services > Developer Tools > SourceCommit menus, in that order.
Select a repository from the SourceCommit page, and then click the [Go to code] button.
- You can also click the repository name from the repository list.
From the Repository's detailed feature page, click the [Pull request] tab.
- You can check opened pull requests in the pull request list.
- You can also set the Status filter on the upper right of the list as Opened to show opened pull requests only in the list.
Click the pull request item to be processed in the pull request list.
Check the detailed change history in the Pull request content area.
- You can click the [Edit] button on the right of the Pull request content to modify the pull request's name and description.
- You can click the [Commits], [Commits], and [Files changed] tabs to check the detailed change history of the branch.
- [Comments] tab: Check the created comment or click the [Add] button to add a new comment.
- [Commits] tab: Click Commit message or Commit item in the commit list to check the commit's change history, HEAD, or the entire commit list.
- [Files changed] tab: Checks each file's detailed modification history in the Compare file window.
Click the following buttons on the right of the Pull request content area to process pull requests.
[Merge]: You can merge the source branch's changes with the target branch through a new commit. Check and modify the following settings in the Merge pop-up window, and then click the [Apply] button.
- Merge strategy: The merge strategy of the change is shown.
- Creator name, Email address: Check the creator's name and email address automatically entered, and change them if required.
- Commit message: Check the default message automatically entered, and change it if required.
[Close pull request]: You can close the pull request. From the Close pull request pop-up window, click the [Close] button.
In the Merge pop-up window, the account information of the logged-in account is automatically entered in the Creator name and Email address items.
- The Creator name is the
user.name
value of the commit to be created. - The Email address is the
user.email
value of the commit to be created.
Resolving a pull request conflict
If you modify the same file in the default (master) branch and newly created branch while creating and using a branch, a conflict occurrence message is shown when creating a pull request.
- You can still create a pull request even though the conflict occurrence message is shown.
- If you open a conflicted pull request from the pull request list, then a message saying that you can't merge changes due to the conflict is shown and the [Merge] button is disabled. In this case, you can't merge.
If a pull request conflict occurs, you can resolve the conflict by using the Git client in the repository copied to a local PC, and then merge the branch.
- Refer to Using Git client for details about using the Git client and copying a repository.
- Refer to the Official Git document for details about resolving a conflict.
The following describes how to resolve a conflict between branches by using the Git client if the source and target branches are "issue" and "master", and the conflicted file is "file.txt."
- Check out from the repository copied to a local PC to the target branch.
$ git checkout master
- Merge the source branch.
- If a conflict between branches is detected, the following message is shown.
$ 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.
- Check the list of files where 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
- Open the file where the conflict occurred, and then check the conflict content shown.
- The conflict content of both branches is shown as follows.
<<<<<<< HEAD
master: content of the target branch
=======
issue: content of the source branch
>>>>>>> issue
Modify the duplicated conflict content, and then save the file.
- Delete the automatically inserted marker part (
<<<<<< HEAD
~>>>>>> issue
) completely before saving the file.
- Delete the automatically inserted marker part (
Upload (push) the modified file to the remote repository (SourceCommit repository).
$ git add file.txt
$ git commit
$ git push
Change repository settings
You can change the repository's default branch and change the description text entered when creating the repository and security product (File Safer) linkage settings, if required.
Change default branch
The following describes how to change a depository's default branch.
- Connect to the NAVER Cloud Platform console.
- Click the Services > Developer Tools > SourceCommit menus, in that order.
- Select a repository from the SourceCommit page, and then click the [Change settings] button.
- Click the Default branch list in the Set repository page, select a branch, and then click the [Save] button.
Update the Git client to a upper version (v1.8.4.3 or later is recommended) if the default branch settings aren't applied properly when opening a repository copied to a local PC using the Git client.
Changing a repository description
The following describes how to change a depository's description.
- Connect to the NAVER Cloud Platform console.
- Click the Services > Developer Tools > SourceCommit menus, in that order.
- Select a repository from the SourceCommit page, and then click the [Change settings] button.
- Modify the description of the Repository description field in the Set repository page, and then click the [Save] button.
Set File Safer linkage
The following describes how to change a repository's File Safer linkage settings.
The File Safer service's usage status is not changed even if you release the repository's File Safer linkage. Cancel a subscription to the File Safer in the service's subscription menu (Services > Security > File Safer > Subscription) to cancel a subscription to the service.
- Connect to the NAVER Cloud Platform console.
- Click the Services > Developer Tools > SourceCommit menus, in that order.
- Select a repository from the SourceCommit page, and then click the [Change settings] button.
- In the Link security product area of the Set repository page, click the checkbox of the Link FILE SAFER (FILE FILTER) product item to select or deselect, and then click the [Save] button.
Delete repository
You can delete a repository no longer in use.
Check once again if the repository is not needed anymore before deleting it. The deleted repository can't be recovered.
The following describes how to delete a repository.
- Connect to the NAVER Cloud Platform console.
- Click the Services > Developer Tools > SourceCommit menus, in that order.
- Select a repository from the SourceCommit page, and then click the [Delete] button.
- Enter the repository name you want to delete in the Delete repository pop-up window, and then click the [Delete] button.
- The [Delete] button isn't enabled before entering the repository name correctly in the Delete repository pop-up window.
- The copy of the repository can remain in the local PC even after the SourceCommit repository is deleted.