Hi ... Im very new to Git/EGit.
I setup a remote repo with gerrit. After creating the master branch I created a develop branch based on the master. These two branches also exists on the remote repo.
Then I created a feature branch. I got a local branch. After changeing code, submitting locally I tried to push this branch to the remote Repo.

Creating a feature branch on Gerrit server is usually done for bigger features which
require collaboration between different developers. Alternatively you may consider
to use patch series, though this is a bit more tricky to maintain as often this requires
using rebase interactive to update the series.

For single changes you don't need to explicitly create server side branches as they
are kept on a virtual branch managed by Gerrit until the change gets accepted in
the code review process.

This is not creating the Branch on the remote repo. Should it? I can not find any? So where did that push to?

Quote:

For single changes you don't need to explicitly create server side branches as they
are kept on a virtual branch managed by Gerrit until the change gets accepted in
the code review process.

Which refs configuration do i have to use to push to the Gerrit Review? As I saw an the Exercise 2: Develop a feature from the Userguide they pushed the feature branch into the master. Isn`t that already a merge?

I do have one more question about the usability of EGit.
Is there a better way to configure the Push refs?

Scenario 1
I switched to Branch develop. After making changes, submitting locally, I would like to push to the remote. To do that I have to change my Push Configuration to HEAD:refs/for/develop.

Scenario 2
I swiched to a feature branch Feature_1. Again made changes, submitted locally. Now I would like to push to the remote feature branch (I already created that branch). To do so I have again to change the Push Configuration to HEAD:refs/for/Feature_1.

Isn`t there a way to save this kind of configurations? Or am I totally misunderstanding the usage of EGit?

So if I click "push" on the push entry under remote "origin"
I push my change to refs/for/master so that the change
gets accepted into master. If I click "push" on remote "stable-1.3"
the change goes into the review queue for the stable-1.3
branch.

This is a local configuration on the receiving end. I think you can't configure that on the server side. AFAIK the reason why git doesn't transport configurations is to protect you against remote git repositories run by some bad guys which might try to compromise your system.