I think stash -p is probably the choice you want, but just in case you run into other even more tricky things in the future, remember that: Stash is really just a very simple alternative to the only slightly more complex branch sets. Stash is very useful for moving things around quickly, but you can accomplish more complex things with … Read more
Simple Git 2.0+ solution: As of Git 2.0, the behavior has become simpler: You can configure git with push.default = current to make life easier: I added this so now I can just push a new branch upstream with -u will track remote branch of the same name. Now with this configuration, you will auto-guess the remote reference to … Read more
Not particularly easily- if you’ve lost the pointer to the tip of a branch, it’s rather like finding a needle in a haystack. You can find all the commits that don’t appear to be referenced any more- git fsck –unreachable will do this for you- but that will include commits that you threw away after a git commit … Read more
All the data Git uses for information is stored in .git/, so removing it should work just fine. Of course, make sure that your working copy is in the exact state that you want it, because everything else will be lost. .git folder is hidden so make sure you turn on the “Show hidden files, folders and disks” … Read more
should show all the local branches of your repo. The starred branch is your current branch. If you want to retrieve only the name of the branch you are on, you can do: or with Git 2.22 and above:
TL;DR: git branch –set-upstream-to origin/solaris The answer to the question you asked—which I’ll rephrase a bit as “do I have to set an upstream”—is: no, you don’t have to set an upstream at all. If you do not have upstream for the current branch, however, Git changes its behavior on git push, and on other commands as well. The … Read more
I have noticed that the two blocks of following git commands have different behaviours and I don’t understand why. I have an A and a B branches that diverge with one commit I want to rebase B branch on the lastest A (and have the commit on the B branch) No problem if I do: But if I do: It doesn’t work at all, nothing happens. … Read more
If you want only the remote URL, or if your are not connected to a network that can reach the remote repo: If you require full output and you are on a network that can reach the remote repo where the origin resides : When using git clone (from GitHub, or any source repository for that matter) the default … Read more
https://[email protected]/eurydyce/MDANSE.git is not an ssh url, it is an https one (which would require your GitHub account name, instead of ‘git‘). Try to use ssh://[email protected]:eurydyce/MDANSE.git or just [email protected]:eurydyce/MDANSE.git The OP Pellegrini Eric adds: That’s what I did in my ~/.gitconfig file that contains currently the following entries [remote “origin”] [email protected]:eurydyce/MDANSE.git This should not be in your global config (the one in ~/).You could check git config … Read more
Use the git diff branch branch filename syntax: put the two names of your branches and optionally use the — filename option to specify one file! Good luck, let me know if you have issues.