As mentioned in the blog post “Start a New Branch on your Remote Git Repository”: Creating a Remote Branch git push origin origin:refs/heads/new_feature_name Make sure everything is up-to-date git fetch origin Then you can see that the branch is created. git branch -r This should show ‘origin/new_feature_name’ Start tracking the new branch git checkout –track … Read more
This is one way: git log –all –name-only –pretty=format: | sort -u | grep _robot.php
According to Wikipedia http://en.wikipedia.org/wiki/Zip_(file_format) seems that zip files have headers for File last modification time and File last modification date so any zip file checked into git will appear to git to have changed if the zip is rebuilt from the same content since. And it seems that there is no flag to tell it … Read more
You can rename branches: git branch -m master newfeaturebranch git branch -m feature1 master
The closest option may be: git push –follow-tags Push all the refs that would be pushed without this option, and also push annotated tags in refs/tags that are missing from the remote but are pointing at committish that are reachable from the refs being pushed.
In my case the SSH-authenticated repository was updated to use LFS from another client and on my side Git-LFS didn’t know about the SSH remote-url. What I did to fix it was the following: Copy the URL configured in remote.origin.url (push URL for origin) to lfs.url (the URL LFS uses): $ git config lfs.url $(git … Read more
You have to explicitly stage changes for commitment by using git add or git rm. If you use the -a flag when doing a commit, git will automatically stage any modified and removed files without you having to explicitly stage them using add or rm, etc. If you don’t specify -a, any files that have … Read more
Sadly, the Visual Studio plugin for Git doesn’t display the error messages you need to troubleshoot this problem. (I hope they plan that feature for a later release.) Try pulling the latest commits using Git Bash or using TortoiseGit. Either of those tools should let you know where your conflicts are.
I have presented that move in “Why doesn’t Git use more modern SHA?” in Aug. 2018 The reasons were discussed here by Brian M. Carlson: I’ve implemented and tested the following algorithms, all of which are 256-bit (in alphabetical order): BLAKE2b (libb2) BLAKE2bp (libb2) KangarooTwelve (imported from the Keccak Code Package) SHA-256 (OpenSSL) SHA-512/256 (OpenSSL) … Read more
(I’ve voted to close this as a possible duplicate, but I might as well add a similar answer anyway.) When using the SSH transport, GitHub identifies you as a user based on the SSH key that you use to authenticate. So, you need to make sure that git is using one SSH key for one … Read more