To get a commit count for a revision (HEAD, master, a commit hash): git rev-list –count <revision> To get the commit count across all branches: git rev-list –all –count I recommend against using this for build identifier, but if you must, it’s probably best to use the count for the branch you’re building against. That … Read more
If the user has not generated a ssh public/private key pair set before This info is working on theChaw but can be applied to all other git repositories which support SSH pubkey authentications. (See [gitolite][1], gitlab or github for example.) First start by setting up your own public/private key pair set. This can use either … Read more
Identify the hash of the commit, using git log, then use git revert <commit> to create a new commit that removes these changes. In a way, git revert is the converse of git cherry-pick — the latter applies the patch to a branch that’s missing it, the former removes it from a branch that has … Read more
git branch –force <branch-name> [<new-tip-commit>] If new-tip-commit is omitted, it defaults to the current commit. new-tip-commit can be a branch name (e.g., master, origin/master).
You have two options: The first is a merge, but this creates an extra commit for the merge. Checkout each branch: git checkout b1 Then merge: git merge origin/master Then push: git push origin b1 Alternatively, you can do a rebase: git fetch git rebase origin/master
Note: the git1.7.10 (April 2012) actually allows you to clone only one branch: # clone only the remote primary HEAD (default: origin/master) git clone <url> –single-branch # as in: git clone <url> –branch <branch> –single-branch [<folder>] (<url> is the URL if the remote repository, and does not reference itself the branch cloned) You can see … Read more
WARNING: it will delete untracked files, so it’s not a great answer to the question being posed. I hit this message as well. In my case, I didn’t want to keep the files, so this worked for me: git 2.11 and newer git clean -d -f . older git git clean -d -f “” If … Read more
The output tells you what you need to do. git reset HEAD cc.properties etc. This will unstage the rm operation. After that, running a git status again will tell you that you need to do a git checkout — cc.properties to get the file back. Update: I have this in my config file $ git … Read more
Assuming that your branch is called master both here and remotely, and that your remote is called origin you could do: git reset –hard <commit-hash> git push -f origin master However, you should avoid doing this if anyone else is working with your remote repository and has pulled your changes. In that case, it would … Read more
GitHub isn’t able to authenticate you. So, either you aren’t setup with an SSH key, because you haven’t set one up on your machine, or your key isn’t associated with your GitHub account. You can also use the HTTPS URL instead of the SSH/git URL to avoid having to deal with SSH keys. This is … Read more