Using Git: When Things Go Wrong

Most of us are pretty comfortable with Git when everything’s going well. But when the worst happens -- when you accidentally delete a vital commit, or you’ve checked something horrible into source control, or a bug pops up and you don’t know where it is or how long it’s been in your code -- it’s all too easy to try fixing things with commands we copied from Stack Overflow and make our problem even worse than it was when we started.
In this session, we’ll learn how Git’s great power can be used for good when things go wrong. Probe the occult secrets of deleted commits with git reflog. Gaze into the heart of darkness and find bugs using git bisect. And learn to change history itself with git squash, git rebase, and amend commits.

Bio:
Sean McMains loves to make awesome stuff: cannons, software, trebuchets, games, music, rockets, pranks, hovercraft, and four kids. He wrote his first software for pay at age 12, and has been programming ever since. He’s been fortunate to be a part of the rise of the web, mobile, and now Extended Reality. He’s currently directing the technology implementation team at Handsome in Austin, Texas.