Is there a “theirs” version of “git merge -s ours”?

A similar alternative is the –strategy-option (short form -X) option, which accepts theirs. For example: However, this is more equivalent to -X ours than -s ours. The key difference being that -X performs a regular recursive merge, resolving any conflicts using the chosen side, whereas -s ours changes the merge to just completely ignore the other side. In some cases, the main problem using -X theirs instead of … Read more

“Key is invalid” message on GitHub

I came here because I had the same problem. From your question, I realized that I was copying the contents from the wrong file, without the .pub extension (it was my private key, i.e. the id_rsa file, which should be kept private at all times!) From a MAC: Copy exactly from the end (with be the last letter of your email … Read more

git – Your branch is ahead of ‘origin/master’ by 1 commit

You cannot push anything that hasn’t been committed yet. The order of operations is: Make your change. git add – this stages your changes for committing git commit – this commits your staged changes locally git push – this pushes your committed changes to a remote If you push without committing, nothing gets pushed. If you commit without … Read more

.gitignore and “The following untracked working tree files would be overwritten by checkout”

It seems like you want the files ignored but they have already been commited. .gitignore has no effect on files that are already in the repo so they need to be removed with git rm –cached. The –cached will prevent it from having any effect on your working copy and it will just mark as removed the next … Read more