...
You can set up the SDNC IDE by following instructions from Setting Up Your Development Environment with the additions described below.
Install sonarlint plugin
<coming soon>
Download the Source Code
Create Your Linux Foundation Account
...
Ensure that you have the following configuraiton set properly:
| GIT Config Key | Expected Value | Setting Command |
|---|---|---|
| core.eol | lf | git config --global core.eol lf |
core.autocrlf | true | git config --global core.autocrlf true |
| user.name | your name | git config --global user.name <your name> |
| user.email | your email address | git config --global user.email <your email address> |
| Anchor | ||||
|---|---|---|---|---|
|
...
2. Run the following commands in the listed order to create a review
| Steps | Command | Notes | |||||||
|---|---|---|---|---|---|---|---|---|---|
| 1 | git commit -sam <comment summary> | Commit summary should not exceed 50 char. See ONAP Commit Messages for more details. | |||||||
| 2 | git log --shortstat | To ensure change lines are properly done and your commit has the following:
Here's an example:
If the Change-Id does not exist, do not proceed. You need to following SDNC - Development Environment Setup to fix it before proceeding further. | |||||||
| 3 | git commit --amend | Use this command to do the following:
| |||||||
| 4 | git review | This command will create the review at Gerrit. Once this command is completed, your newly created review can be found from Outgoing reviews in Gerrit self dashboard . |
3. Update the Gerrit Review to get ready
...
Go back to your workspace, and do the following to change the comments of your existing review.
| Steps | Command | Notes |
|---|---|---|
| 1 | git commit --amend | update the comment as desired |
| 2 | git log --shortstat | validate your commit now has the updated comments, as well as the Change-Id as the one in the gerrit review |
| 3 | git review | push the changed comment to the review again. Once the command is completed, go to your review, you will see
|
How to Update the Code in A Review
...
Follow the steps to push your new code changes to the your existing reiew.
| Steps | command | notes |
|---|---|---|
| 1 | git commit -sam "my updated code" | To create a new commit with your updated code |
| 2 | git log --shortstat | you will see the most 2 recent commits are from
|
| 3 | git rebase -i HEAD~2 | To run rebase interactively for the most recent 2 commits In the interactive mode, it will bring up the text which contains pick for your last 2 commits along with the following content:
Do the following:
Once this command is completed, 2 commits will be merged into 1 commit. |
| 4 | git log --shortstat | you will see there's only 1 commit which replaces the 2 commit you have seen in step 2. validate your commit has the Change-Id as the one in the gerrit review |
| 5 | git review | push the changed comment to the review again. Once the command is completed, go to your review, you will see
|
| Anchor | ||||
|---|---|---|---|---|
|
...
Follow the steps below to do the correction.
| Steps | Command | Notes |
|---|---|---|
| 1 | git reset HEAD~1 | to undo the commit |
| 2 | from github helper page, download commit-msg, and place it under your <repo>/.git/hook directory | set the proper commit-msg hook this will set the Change-Id properly in your commit |
| 3 | Use your previous command to create the commit again | |
| 4 | git log --shortstat | to check the existence of Change-Id |
How to Find All of My Merged Changes
...