If you followed the wiki on setting up a git connection

This part consists of multiple steps. The plan is as follows:

1. Add changed files to stage
2. Create a commit
3. Push to the forked (your own) project

To keep it simpler, the changes are pushed to the main branch of the fork repository. The following steps can also be done on other branches if larger subprojects or bugfixes are to be developed.

In Eclipse, make sure that the `Git Staging View` is visible. Click on <key>Window</key> > <key>Show View</key> > <key>Git Staging</key>.

The area will appear in the lower part of the window of Eclipse (by default in the same tab menu as the search result area console area).

In that area, all changed files are listed in the upper text field. Select one file and click on the green <key>+</key> button or click on the green <key>++</key> button to stage one or all files.

Then, click on <key>Commit and Push…</key>. The current branch and the fitting remote branch should already be selected. Make sure that your fork repository and the correct remote branch are selected. Then click on <key>Commit and Push</key>.

After the push interaction, Eclipse shows a status window. This shows a summary of the executed steps and can be closed with <key>OK</key>.

Go to your fork project in the internet browser.

In the left sidebar, click on <key>Merge Requests</key>.

Then click on <key>New merge request</key>.

Select the correct source project (your fork project) and the correct source branch (the path you pushed to in Eclipse).

Select the correct target project (grogra/groimp) and the correct target branch. Ask an experienced developer of the GroIMP developer team for the correct branch, depending on what you developed or improved.

Then click on <key>Compare branches and continue</key>.

You can also open issues in gitlab to notify on a bug, a possible improvement, or a discussion on the development of GroIMP.