Once you get a “Code-Review: +2” from a Go contributor, your change will be merged! Need help? Then in the Gerrit UI, find the in-line comments left by your reviewer, click “Done”, go back to the main PR page, and click “Reply” => “Send” to tell your reviewer that you've addressed your feedback. Your commit message should still summarize the entire commit (“Add kevinburke/main.go”), not just the change a reviewer asked for (“Fix typo”).Īfter you amend the commit, re-run git codereview mail to push that change to the server. To amend a previous commit, run git add (list of files you changed) to add your changes, then run git commit -amend to amend the commit to add new data. By contrast, all changes opened in Gerrit are a single commit, which means you need to amend your commit if the reviewer requests feedback. If you have needed to change a Github pull request, you probably just added a second commit with the requested changes and pushed it. You can put whatever you want in your main function see the existing directories for examples.Īll files should have the standard licensing header, and add appropriate documentation see the other files in this repository for an example. What should I add?Īdd a folder with your username, and put a main function in there.
#Gobot tutorial how to
This repository is mainly for use by people learning how to use Gerrit and contribute to Go.Ĭlick here for a tutorial on how to get started with a contribution to this repository.Ī fuller, text-based tutorial based around the core Go project can be found here.
0 kommentar(er)
