git push doesn’t push all of your local branches: how would it know which remote branches to push them to? It only pushes local branches which have been configured to push to a particular remote branch. On my version of Git (1.6.5.3), when I run git remote show origin it actually prints out which branches are configured for … Read more
Instead of removing and re-adding, you can do this: See this question: How to change the URI (URL) for a remote Git repository? To remove remote use this:
You can use the following command: … which will update both the working copy of my-file.txt and its state in the index with that from HEAD. — basically means: treat every argument after this point as a file name. More details in this answer. Thanks to VonC for pointing this out.
You can use the following command: … which will update both the working copy of my-file.txt and its state in the index with that from HEAD. — basically means: treat every argument after this point as a file name. More details in this answer. Thanks to VonC for pointing this out.
Your Git is complaining that a reference (rather than a directory) named refs/tags exists. It’s not clear what would create that, but see if git rev-parse refs/tags produces a hash ID. If so, that reference needs to go away: after which git fetch should work. If git rev-parse refs/tags fails (which it should—refs/tags itself should not be a valid name) then this is not the problem and it’s … Read more
The problem is that you are not tracking the files locally but identical files are tracked remotely so in order to “pull” your system would be forced to overwrite the local files which are not version controlled. Try running This will track all files, remove all of your local changes to those files, and then … Read more
Adapting the PATH should work. Just tried on my Git bash: In particular, only provide the directory; don’t specify the .exe on the PATH ; and use slashes.
Your local branch doesn’t know about the remote branch. If you don’t tell git that your local branch (master) is supposed to compare itself to the remote counterpart (origin/master in this case); then git status won’t tell you the difference between your branch and the remote one. So you should use: or with the short option: This options –set-upstream-to (or -u in … Read more
If your excess commits are only visible to you, you can just do git reset –hard origin/<branch_name> to move back to where the origin is. This will reset the state of the repository to the previous commit, and it will discard all local changes. Doing a git revert makes new commits to remove old commits in a way that keeps everyone’s history sane.
The wiki is talking from a forked repo point of view. You have access to pull and push from origin, which will be your fork of the main diaspora repo. To pull in changes from this main repo, you add a remote, “upstream” in your local repo, pointing to this original and pull from it. … Read more