Git and Gerrit FAQ
- 1 Git
- 1.1 Pulling
- 1.2 Committing
- 1.3 Submitting for review
- 2 Gerrit
- 3 See also
Should I use
git pull origin master or
git pull gerrit master?
Unless you're a git expert, they should be the same. The remote repository "gerrit" is the "origin" for the code of Wikimedia projects. Change directory to a repository and enter enter git remote -v to see what remotes uses.
As Gerrit/Tutorial#Configuring git-review says, you can put
[gerrit] defaultremote = origin
in ~/.config/git-review/git-review.conf to ensure this.
There used to be instructions for eliminating any duplications, somewhere
It says "Please, commit your changes or stash them before you can merge." What do I do?
To discard your changes (and anything you had in the stash):
git stash git stash clear
Now you can proceed with your pull.
What's the difference between
git commit --amend and
git commit --amend -a?
The -a option automatically stages all tracked, modified files before the commit, letting you skip the
git add step unless you need to start tracking new files. A tracked file is a file that was in your last commit.
Submitting for review
When should I use
git review -R rather than just
How do I save inline code comments? I can only save them as drafts.
- When I comment on code inline or reply to comments inline I cannot save it properly, just as a draft.
A: It's another of Gerrit's unintuitive parts. You have to click the "review" button back in the change overview page, and the draft inline comments will be attached to your "global" comment when you save it.
What should I put in the cover message when I publish comments?
How do I watch changes?
A: You have to watch projects. See Gerrit/watched projects.
- For example, for bugs I can use [[bugzilla:1234|bug 1234]] to produce bug 1234.
A: To link to revision 1234 use [[gerrit:1234|revision 1234]]: revision 1234.