The idea behind git bisect is to perform a binary search in the history to find a particular regression. Imagine that you have the following development history: … — 0 — 1 — 2 — 3 — 4* — 5 — current You know that your program is not working properly at the current revision, … Read more
Yes, you may put comments in there. They however must start at the beginning of a line. cf. http://git-scm.com/book/en/Git-Basics-Recording-Changes-to-the-Repository#Ignoring-Files The rules for the patterns you can put in the .gitignore file are as follows: – Blank lines or lines starting with # are ignored. […] The comment character is #, example: # no .a files … Read more
Before executing this command, keep in mind that it will leave you in a detached head status. Use git checkout <sha1> to check out a particular commit. Where <sha1> is the commit unique number (SHA-1 hash value) that you can obtain with git log. Here are some options after you are in the detached head … Read more
Use the BFG Repo-Cleaner, a simpler, faster alternative to git-filter-branch, specifically designed for removing unwanted files from Git history. Carefully follow the usage instructions. The core part is just this: java -jar bfg.jar –strip-blobs-bigger-than 100M my-repo.git Any files over 100 MB in size (that aren’t in your latest commit) will be removed from your Git … Read more
Not natively (VS Code) or with GitLens (GitHub repo) As you probably know (or written), there is a feature request Right now, I know which lines are not staged (green for new, blue for edited) and maybe when I commit locally, highlight those lines in a different color (purple?) to represent “committed but unpublished.” But … Read more
You may check pastgit: git backed paste server (gist python clone) https://github.com/mmikulicic/pastgit Also gitpaste: (another gist clone based on Django) https://github.com/justinvh/gitpaste
According to your answers in the comments, executing git diff HEAD^ will not help you, except if you only want to reword the last commit. But in this case a rebase is the wrong tool anyway. Instead you can simply do git commit –amend –verbose without changes in the index and then edit the commit … Read more
Unfortunately this cannot be done. See Continue interrupted git clone No. git clone cannot be restarted. You’ll need to rm -rf common, and then restart then clone from the beginning. Continue git clone after interruption Unfortunately, we did not have enough GSoC slots for the project to allow restartable clones. There were discussions about how … Read more
They do two different things . Let say , you did GIT PULL and then started editing some files and probably have added and commited those changes to the be pushed … and then for some reason you decided to just discard all the changes that have been made to the given files and go … Read more
You could write a setup script, e.g. setuphooks.sh, that pulls down the hook scripts and installs them in the right places. It shouldn’t be hard to write, as curl could do most of the work. Or you could just include the hooks in the repo in a normal folder like .hooks, and copy them all … Read more