#sorting

You can checkout the branch of the merge request, run git reset --hard 6.3.x, make your changes, then git push --force. That will re-use the current merge request. It will automatically create a tag pointing at the old commits so they are there to refer to. Nothing gets lost.

Answer to #6: I think I messed up the branch on previous merge request and it seemed to be rather cumbersome to fix. I tried to merge the 6.3.x to the branch that was based on 6.2.x so it had all the changes shown as they are coming in on my merge request as a new files and chagnes. Closed that and created new branch based on 6.3.x and added code there as it was before. Still haven't made tests, but they are coming in the near future and then I will open the request again.

There is no need to close the merge request. It can be updated to point to branch 6.3.x and you can force-push the updated code to the feature branch of the merge request.

konstara → closed merge request !411