Page History

...

1. Clone the repo that your contribution is for:  git clone http://gerrit.o-ran-sc.org/r/<REPO_PATH>

2. Change dir into the repo;

3. Sign for your code change:  git review -s;   This is where Gerrit plugin using ssh to verify with gerrit.o-ran-sc.org that your email is already registered with the server;
4. Follow the usual git code change work flow: make code change, git add, and git commit;
   1. The message provided at git commit should be used as commit summary, --keep it short;
5. Update commit message with git commit -s --amend;  This is where more detailed commit messages are added, and a signed-off by line inserted to commit message;
6. Submit code change with git review;

After the initial code change submit, if further changes (patches) are needed for the same submission, we can make the change and git add, then use git commit -s --amend to commit and modify the commit message, then git review to submit for code review.  Do not use just git commit, as it will create a new change ID and causing the new patch to be submitted as a new change instead of a patch atop of the existing code submission.

...