If you enabled two-factor authentication in your GitHub account you won’t be able to push via HTTPS using your accounts password. Instead you need to generate a personal access token. This can be done in the application settings of your GitHub account. Using this token as your password should allow you to push to your … Read more
Here is a command that gives you all tracking branches (configured for ‘pull’), see: $ git branch -vv main aaf02f0 [main/master: ahead 25] Some other commit * master add0a03 [jdsumsion/master] Some commit You have to wade through the SHA and any long-wrapping commit messages, but it’s quick to type and I get the tracking branches … Read more
If you hadn’t made any commit yet, only (1: branch) and (3: checkout) would be enough. Or, in one command: git checkout -b newBranch With Git 2.23+ (Q3 2019), the new command git switch would create the branch in one line (with the same kind of reset –hard, so beware of its effect): # First, … Read more
I think that Git on Dropbox is great. I use it all the time. I have multiple computers (two at home and one at work) on which I use Dropbox as a central bare repository. Since I don’t want to host it on a public service, and I don’t have access to a server that … Read more
You need to set up your global core.excludesfile configuration file to point to this global ignore file e.g: *nix or Windows git bash: git config –global core.excludesFile ‘~/.gitignore’ Windows cmd: git config –global core.excludesFile “%USERPROFILE%\.gitignore” Windows PowerShell: git config –global core.excludesFile “$Env:USERPROFILE\.gitignore” For Windows it is set to the location C:\Users\%username%\.gitignore. You can verify that … Read more
This will unstage all files you might have staged with git add: git reset This will revert all local uncommitted changes (should be executed in repo root): git checkout . You can also revert uncommitted changes only to particular file or directory: git checkout [some_dir|file.txt] Yet another way to revert all uncommitted changes (longer to … Read more
After pruning, you can get the list of remote branches with git branch -r. The list of branches with their remote tracking branch can be retrieved with git branch -vv. So using these two lists you can find the remote tracking branches that are not in the list of remotes. This line should do the … Read more
There are a few ways to accomplish that: Change your local branch and then push your changes Push the branch to remote with the new name while keeping the original name locally Renaming local and remote # Rename the local branch to the new name git branch -m <old_name> <new_name> # Delete the old branch … Read more
IF you have NOT pushed your changes to remote git reset HEAD~1 Check if the working copy is clean by git status. ELSE you have pushed your changes to remote git revert HEAD This command will revert/remove the local commits/change and then you can push
Based on Michael Scharf’s comment: You can leave out the password so that it won’t be logged in your Bash history file: git clone https://username@github.com/username/repository.git It will prompt you for your password. Alternatively, you may use: git clone https://username:password@github.com/username/repository.git This way worked for me from a GitHub repository.