If you are using two-factor authentication with GitHub you will need to create a personal access token and use it with SourceTree: To work with GitHub’s two-factor authentication in SourceTree you can simply use your access token instead of your password. The steps to do this are as follows: Go to your Personal Access Tokens … Read more
I think your basic issue here is that you’re misinterpreting and/or misunderstanding what git does and why it does it. When you clone some other repository, git makes a copy of whatever is “over there”. It also takes “their” branch labels, such as master, and makes a copy of that label whose “full name” in … Read more
For some git-commands you can specify –verbose, or Make sure the switch is after the actual git command. Otherwise – it won’t work! Also useful:
If you checkout a commit sha directly, it puts you into a “detached head” state, which basically just means that the current sha that your working copy has checked out, doesn’t have a branch pointing at it. If you haven’t made any commits yet, you can leave detached head state by simply checking out whichever branch you … Read more
Git hub has removed TLS-1.0 from it’s authentication services. https://githubengineering.com/crypto-removal-notice/ Solutions Windows Clients Use Version 2.14.3 (or newer) of Git for Windows and newer include an up-to-date Git Credential Manager for Windows: https://gitforwindows.org/ You can also explicitly update your Git Windows Credencial Manager to the latest version, 1.14.0, to get TLS-1.2 support: https://github.com/Microsoft/Git-Credential-Manager-for-Windows/releases/tag/v1.14.0 Visual Studio … Read more
HEAD points to the top of the current branch. git can obtain the branch name from that. So it’s the same as: but you don’t have to remember/type the current branch name. Also it prevents you from pushing to the wrong remote branch by accident. If you want to push a different branch than the current one the … Read more
HEAD points to the top of the current branch. git can obtain the branch name from that. So it’s the same as: but you don’t have to remember/type the current branch name. Also it prevents you from pushing to the wrong remote branch by accident. If you want to push a different branch than the current one the … Read more
if you just want them to be the same thing then
Basically git commit “records changes to the repository” while git push “updates remote refs along with associated objects“. So the first one is used in connection with your local repository, while the latter one is used to interact with a remote repository. Here is a nice picture from Oliver Steele, that explains the git model … Read more
Probably the simplest way to achieve this is with git archive. If you really need just the expanded tree you can do something like this. Most of the time that I need to ‘export’ something from git, I want a compressed archive in any case so I do something like this. ZIP archive: git help archive for … Read more