Hi,
Please check out also this guide: https://www.coreboot.org/Git#Pushing_changes
you need to tell git where to push: `HEAD:refs/for/master`. It seems the guide on https://doc.coreboot.org/tutorial/part2.html is missing one crucial step:
`git config remote.origin.push HEAD:refs/for/master`
You don't need any particular rights to push. You have two options to authorize:
1. SSH key (add SSH key to gerrit account and configure git remote for SSH or simply clone with SSH like here https://www.coreboot.org/Git#Accessing_the_repository) 2. HTTP password. If you cloned the repo by HTTP(S) then you should be asked for password. You can generate it on your gerrit account.
Even if you skip the git config commands, `git push origin HEAD:refs/for/master` should push your commit(s) you have added on top of your local master branch to gerrit. They will be public. if you append %private at the end of the command, it will be private. If you append %wip it will be marked as work in progress.
Of course we can't see it if it is private. You would have to add reviewers or people on CC.
Who to add as reviewer? It depends what the patch does. You may suggest reviewers by looking at MAINTAINERS file in the repo which contains the people who are more familiar with given part of coreboot source and can provide good reviews.
How to add reviewer? If your press reply button above the commit message on gerrit (when displaying your patch) a window will pop up. You may skip writing any message. Just click in the row with reviewers (where Add reviewer is written) and start typing. Auto completion should give you some results. Type by name, nick or email of the reviewer.
Best regards,