Skip to content

git.md

Latest commit

 

History

History
19 lines (13 loc) · 1.38 KB

git.md

File metadata and controls

19 lines (13 loc) · 1.38 KB

Debugging credential problems

Usually these related to communication between ssh and git. If you run the offending git command with GIT_TRACE=true set, you'll likely see an ssh command it tries to run. Then you can try running the ssh command manually but with a -vvvv added option to see what ssh has to say about the situation. ssh debugging logs are usually clear and on point.

Using separate key for specific host

Given a example.com domain and a key pair ~/.ssh/my-key and ~/.ssh/my-key.pub, create a ~/.ssh/config file:

Host example.com
    IdentityFile ~/.ssh/my-key
    IdentitiesOnly yes

Misc

  • HEAD~n syntax: works reliably only in absence of merge commits. If those are present, then it only counts the merge commit, entirely ignoring the commits that were brought by it.
  • resetting bisect without causing it to checkout somewhere: git bisect reset HEAD
  • bisecting specific subset of commits: e.g. you might know your problem is likely in FOO subsystem of the project. Bisection can be limited to just it by starting bisect explicitly with a list of paths, like git bisect start -- path1/FOO path2. Known problem: it isn't able to dive into between commits modifying those paths if turned out to be the problem is not in one of them. So you'll have to reset bisect at this point, and restart it again by using last known good/bad commits pair.