To avoid changing your git config, you can enable colour just for the current command by passing a config variable with -c. For the status command, the variable is color.status: git -c color.status=always status | less -REX For diff, show, log and grep commands, the variable is color.ui: git -c color.ui=always diff | less -REX … Read more
git diff –stat will show you the output you get when committing stuff which is the one you are referring to I guess. git diff –stat For showing exactly the line numbers that has been changed you can use git blame -p <file> | grep “Not Committed Yet” And the line changed will be the … Read more
Just add a file .gitkeep in every folder you want committed. On windows do so by right clicking when in the folder and select: Git bash from here. Then type: touch .gitkeep
A simple solution I used: Do git reset HEAD^ for as many commits you want to undo, it will keep your changes and your actual state of your files, just flushing the commits of them. Once the commits are undone, you can then think about how to re-commit your files in a better way, e.g.: … Read more
In your case, use git filter-branch instead of git rm. git rm will delete the files in the sense that they will not be tracked by git anymore, but that does not remove the old commit objects corresponding to those images, and so you will still be stuck with pushing the earlier commits which correspond … Read more
Recently, I have seen this problem too. Below, you have my solution: ping github.com, if ping failed. it is DNS error. sudo vim /etc/resolv.conf, the add: nameserver 8.8.8.8 nameserver 8.8.4.4 Or it can be a genuine network issue. Restart your network-manager using sudo service network-manager restart or fix it up
The warning: remote HEAD refers to nonexistent ref, unable to checkout. means that the remote (bare) repository contains branch reference in the file called HEAD with a value that does not match any published branch in the same repository. In practice, that file defines which branch should be checked out by default after cloning the … Read more
I believe you can do: git reset HEAD@{1} To go one commit forward in time. To go forward multiple commits, use HEAD@{2}, HEAD@{3}, etc.
if you happen to not have a graphical interface available you can also print out the commit graph on the command line: git log –oneline –graph –decorate –all if this command complains with an invalid option –oneline, use: git log –pretty=oneline –graph –decorate –all
I followed VonC’s advice: git config –global http.postBuffer 524288000 For future references, based on comments: 500 MB: 524288000 (as posted in the original answer) 1 GB: 1048576000 2 GB: 2097152000 (anything higher is rejected as ‘out of range’)