Upgrading Gitlab

Gitlab follows semantiv versioning. It even does not allow you to upgrade from a non-latest minor version to a new major version. Meaning: 10.1 -> 11.4 is now allowed if there is a 10.8 version. Thus you need to upgrade in steps: 10.1 -> 10.8 -> 11.4 (for example). Procedure: # Create a backup (Don’t… Continue Reading Upgrading Gitlab

git clone on Windows running into host trust/accept host key dead lock

If you are getting $ git clone git@github.com:worp1900/my-project.git Cloning into ‘my-project’… The server’s host key is not cached in the registry. You have no guarantee that the server is the computer you think it is. The server’s rsa2 key fingerprint is: ssh-rsa 2048 github:key If you trust this host, enter “y” to add the key… Continue Reading git clone on Windows running into host trust/accept host key dead lock

Git rebase –onto and the in detached HEAD

Sometimes I branch off of the wrong branch. So I need to rebase my branch onto the correct branch. > git checkout myCurrentBranch > git rebase -i –onto <targetBranch> <fromCommit> <toCommit> Meaning: “git rebase¬†myCurrentBranch¬†onto targetBranch, moving moving all commits since myCurrentBranch diverged from fromCommit until toCommit to targetBranch.” More information: More-interesting-rebases This often times results… Continue Reading Git rebase –onto and the in detached HEAD

error: There was a problem with the editor ‘vi’. Please supply the message using either -m or -F option.

How do deal with
`error: There was a problem with the editor ‘vi’. Please supply the message using either -m or -F option.`
when writing git commit messages. Continue Reading error: There was a problem with the editor ‘vi’. Please supply the message using either -m or -F option.