Contribute to a code review by adding comments to the review, adding comments to specific lines within the review's files, or making edits to the review's files.
To hide the description comments, click X Comments (where X is the number of description comments that exist). To display the comments again, click X Comments.
Get a local copy of the review's files.
Prepare a changelist with the edited files and include #review-1234
within the changelist's description (separated from other text with whitespace, or on a separate line), where 1234
is the review's identifier.
If you use an invalid review identifier, it will appear that nothing happens. Swarm is currently unable to notify you of this situation. If the review has not been correctly updated, use the Add Change button in the Swarm review heading to add the changelist to the review, see Add a changelist to a review.
Depending on the model of code review you are using, you would:
You can only update Git Fusion-initiated reviews using Git Fusion.
In the following example, the current local task branch is task1
, the target branch is master
, the review id is 1234
, the Git Fusion hostname is gfserver
, and the remote repo name is p4gf_repo
.
Fetch the review's head version:
$ git fetch --prune origin From gfserver:p4gf_repo * [new_branch] review/master/1234 -> origin/review/master/1234 x [deleted] (none) -> origin/review/master/new
The --prune
option lets the local Git repo delete the unwanted review/master/new reference created by the initial git push origin task1:review/master/new
command.
Check out the review's head version:
$ git checkout review/master/1234
Add the edited files to the index of files, in preparation for the next commit.
There are several ways to do this. For example, to add all modified files to the index, run:
$ git add -A
Commit the files in Git:
$ git commit -m "made some changes"
Push the Git changes to the review:
$ git push origin review/master/1234
If you get review feedback that is better expressed as a Git rebase and cleaned up history, you can make your changes and push them as a new review.
You cannot clean up history and then push your changes to the same review.
For more information on Git Fusion, see the Git Fusion Guide.