You have a very clear explanation of how this works in the chapter on Acenstry References in Pro Git: ~ is used to get the first parent. ^ can be used to get the other parents (^2, for example, for a merge). But you don’t have a simple way to reference the next commit, even … Read more
I started getting the same error messages for every service after my last upgrade. I made them go away by creating an alias for credential-manager. git config –global alias.credential-manager “credential-manager-core” Other than the error messages, the credential-manager seems to have been working correctly both before and after creating the alias.
A merge commit is just like another commit, the state of your repository at a given point in time plus the history it evolved from. The one thing special about a merge commit is that it has at least two predecessors, therefore a plain vanilla diff doesn’t make sense, you can only compare the merge … Read more
That’s caused by the different standards used in line endings (LineFeed or LF in Linux and CarriageReturn + LineFeed or CRLF in Windows). You can set the encoding you want by either of the following ways: Click the LF or CRLF button on the status bar (near the bottom right corner), then select LF or … Read more
The correct way to do this is to use git log as follows. git log -1 –pretty=”format:%ci” /path/to/repo/anyfile.any -1 restricts it to the very last time the file changed %ci is just one of the date formats you can choose from others here at https://git-scm.com/docs/pretty-formats
For me none of the suggested solutions worked so I tried to fix it myself and I resolved it. I was getting this error on my AWS EC2 UBUNTU instance. I edited the ssh config (or add it if it does not exist). nano ~/.ssh/config And I added the following Host github.com Hostname ssh.github.com Port … Read more
Here’s how to do it with rebase and keep both the commit date and the author date: git -c rebase.instructionFormat=”%s%nexec GIT_COMMITTER_DATE=”%cD” GIT_AUTHOR_DATE=”%aD” git commit –amend –no-edit –reset-author” rebase -f <commit/branch before wrong author and email, or –root to rebase all> Based off this Reddit thread.
The “size” of a commit can mean different things. If you mean how much disk storage it takes up… that’s very tricky to tell in Git and probably unproductive. Whereas something like SVN stores commits as deltas, when you change a file in Git it stores a new copy of the file as an object … Read more
A simple git fetch –tags worked for me.
Use the Gitlens extension. It supports various options. Once installed, you can use Alt+B to show the full file blame information.