I’m trying to understand how GitLab makes merge commit. Pure git has different behaviour and it’s not so clear why merge commits are required in GitLab

I have two machines. I have gitlab repo cloned on one of them and is working just fine.
Recently I tar zipped one folder from this machine and installed the same on the other machine. (.git directory got copied along with it).

https://docs.gitlab.com/ee/api/projects.html#languages

Backstory: There was one frontend repo(let’s call it repo A) in my organization which had casing issues in names of folders, I renamed a folder to confirm it with casing of other folders. During this adventure I noticed that git doesn’t support folder rename, I looked up on stackoverflow for help and somehow was able to rename the folder, then commit some changes into the files of that particular folder.

When I push code that I’ve committed (using git push), I get a very nice, helpful message from the gitlab server that includes a link I can immediately use to set up a merge request. It looks something like this:

I have a Committed a changes on local and I fetch and pull form remote. Then after pull i got an error related to index out of bound But the pull Activity is a success one. After that I push my changes to remote.

Can I create a merge request, via command line, that would be the equivalent of a force push?

For some weird reason I do not yet understand when pushing to GitLab this project with a folder called hooks

For some weird reason I do not yet understand when pushing to GitLab this project with a folder called hooks

I’ve recently encountered the issue that Gitlab returns the error Your git username is inconsistent with Gitlab account name whenever I try to push anything.